Device control using gaze information

ABSTRACT

The present disclosure generally relates to controlling electronic devices. In some examples, the electronic device uses gaze information to activate a digital assistant. In some examples, the electronic device uses gaze information to identify an external device on which to act. In some examples, the electronic device provides an indication that distinguishes between different speakers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/553,622, entitled “DEVICE CONTROL USING GAZE INFORMATION”, filed onAug. 28, 2019, which claims priority to U.S. Provisional App Ser. No.62/739,087, entitled “DEVICE CONTROL USING GAZE INFORMATION”, filed onSep. 28, 2018, the contents of which are hereby incorporated byreference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for controlling electronic devicesusing gaze information.

BACKGROUND

Users frequently provide inputs, such as keypresses and voice inputs, tocontrol electronic devices. For example, users activate a device'sbutton or speak a trigger phrase to start an application on the device.Such inputs frequently require the user to be within arm's reach orwithin microphone range.

Intelligent automated assistants (or digital assistants) can provide abeneficial interface between human users and electronic devices. Suchassistants can allow users to interact with devices or systems usingnatural language in spoken and/or text forms. For example, a user canprovide a speech input containing a user request to a digital assistantoperating on an electronic device. The digital assistant can interpretthe user's intent from the speech input, operationalize the user'sintent into a task, and perform the task. In some systems, performingtasks in this manner may be constrained in the manner by which a task isidentified. In some cases, however, a user may be limited to aparticular set of commands such that the user cannot readily instruct adigital assistant to perform a task using natural-language speechinputs. Further, in many instances digital assistants fail to adaptbased on previous user behavior and in turn lack a desirableoptimization of user experience.

BRIEF SUMMARY

Some techniques for controlling electronic devices, however, aregenerally cumbersome and inefficient. For example, some existingtechniques use a complex and time-consuming user interface, which mayinclude multiple key presses or keystrokes. For another example, someexisting techniques require the user to be within arm's distance toactivate a button of the device. Existing techniques require more timethan necessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for controlling electronicdevices. Such methods and interfaces optionally complement or replaceother methods for controlling electronic devices. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges. Such techniques also allow users to moreefficiently interact with electronic devices in environments where theuser is not within reaching distance of the electronic device and/or theuser is in a noisy environment (e.g., including noise based on audiobeing produced by the electronic device).

In accordance with some embodiments, a method is provided. The method isperformed at an electronic device. The method comprises: while a digitalassistant of the electronic device is not activated: obtaining, usingone or more camera sensors, first gaze information; and in accordancewith a determination that the first gaze information satisfies a set ofone or more activation criteria: activating the digital assistant of theelectronic device; and providing an indication that the set of one ormore activation criteria has been satisfied.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: while adigital assistant of the electronic device is not activated: obtaining,using one or more camera sensors, first gaze information; and inaccordance with a determination that the first gaze informationsatisfies a set of one or more activation criteria: activating thedigital assistant of the electronic device; and providing an indicationthat the set of one or more activation criteria has been satisfied.

In accordance with some embodiments, a transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: while adigital assistant of the electronic device is not activated: obtaining,using one or more camera sensors, first gaze information; and inaccordance with a determination that the first gaze informationsatisfies a set of one or more activation criteria: activating thedigital assistant of the electronic device; and providing an indicationthat the set of one or more activation criteria has been satisfied.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:while a digital assistant of the electronic device is not activated:obtaining, using one or more camera sensors, first gaze information; andin accordance with a determination that the first gaze informationsatisfies a set of one or more activation criteria: activating thedigital assistant of the electronic device; and providing an indicationthat the set of one or more activation criteria has been satisfied.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: means, while a digital assistant of theelectronic device is not activated, for: obtaining, using one or morecamera sensors, first gaze information; and means, in accordance with adetermination that the first gaze information satisfies a set of one ormore activation criteria, for: activating the digital assistant of theelectronic device; and providing an indication that the set of one ormore activation criteria has been satisfied.

In accordance with some embodiments, a method is provided. The method isperformed at an electronic device. The method comprises: while a firstexternal device is in a first state: receiving an audio user inputrequest to perform a first command; and obtaining, using one or morecamera sensors, first gaze information; and in accordance with adetermination, using the first gaze information, that a set of one ormore gaze criteria is met for the first external device: transmitting,based on the first command, an instruction to transition the firstexternal device from the first state to a second state.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: while afirst external device is in a first state: receiving an audio user inputrequest to perform a first command; and obtaining, using one or morecamera sensors, first gaze information; and in accordance with adetermination, using the first gaze information, that a set of one ormore gaze criteria is met for the first external device: transmitting,based on the first command, an instruction to transition the firstexternal device from the first state to a second state.

In accordance with some embodiments, a transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: while afirst external device is in a first state: receiving an audio user inputrequest to perform a first command; and obtaining, using one or morecamera sensors, first gaze information; and in accordance with adetermination, using the first gaze information, that a set of one ormore gaze criteria is met for the first external device: transmitting,based on the first command, an instruction to transition the firstexternal device from the first state to a second state.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:while a first external device is in a first state: receiving an audiouser input request to perform a first command; and obtaining, using oneor more camera sensors, first gaze information; and in accordance with adetermination, using the first gaze information, that a set of one ormore gaze criteria is met for the first external device: transmitting,based on the first command, an instruction to transition the firstexternal device from the first state to a second state.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: means, while a first external device isin a first state, for: receiving an audio user input request to performa first command; and obtaining, using one or more camera sensors, firstgaze information; and means, in accordance with a determination, usingthe first gaze information, that a set of one or more gaze criteria ismet for the first external device, for: transmitting, based on the firstcommand, an instruction to transition the first external device from thefirst state to a second state.

In accordance with some embodiments, a method is provided. The method isperformed at an electronic device. The method comprises: receiving anaudio user input request; in accordance with a determination that theaudio user input request corresponds to a first user, updating a valueof a characteristic of an indicator to a first value corresponding tothe first user; in accordance with a determination that the audio userinput request corresponds to a second user, different from the firstuser, updating the value of the characteristic of the indicator to asecond value corresponding to the second user, the second value beingdifferent from the first value; and responding to the audio user inputrequest using the indicator, wherein the indicator includes the updatedvalue of the characteristic.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: receivingan audio user input request; in accordance with a determination that theaudio user input request corresponds to a first user, updating a valueof a characteristic of an indicator to a first value corresponding tothe first user; in accordance with a determination that the audio userinput request corresponds to a second user, different from the firstuser, updating the value of the characteristic of the indicator to asecond value corresponding to the second user, the second value beingdifferent from the first value; and responding to the audio user inputrequest using the indicator, wherein the indicator includes the updatedvalue of the characteristic.

In accordance with some embodiments, a transitory computer-readablestorage medium is provided. The medium stores one or more programsconfigured to be executed by one or more processors of an electronicdevice. The one or more programs including instructions for: receivingan audio user input request; in accordance with a determination that theaudio user input request corresponds to a first user, updating a valueof a characteristic of an indicator to a first value corresponding tothe first user; in accordance with a determination that the audio userinput request corresponds to a second user, different from the firstuser, updating the value of the characteristic of the indicator to asecond value corresponding to the second user, the second value beingdifferent from the first value; and responding to the audio user inputrequest using the indicator, wherein the indicator includes the updatedvalue of the characteristic.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:receiving an audio user input request; in accordance with adetermination that the audio user input request corresponds to a firstuser, updating a value of a characteristic of an indicator to a firstvalue corresponding to the first user; in accordance with adetermination that the audio user input request corresponds to a seconduser, different from the first user, updating the value of thecharacteristic of the indicator to a second value corresponding to thesecond user, the second value being different from the first value; andresponding to the audio user input request using the indicator, whereinthe indicator includes the updated value of the characteristic.

In accordance with some embodiments, an electronic device is provided.The electronic device comprises: means for receiving an audio user inputrequest; means, in accordance with a determination that the audio userinput request corresponds to a first user, for updating a value of acharacteristic of an indicator to a first value corresponding to thefirst user; means, in accordance with a determination that the audiouser input request corresponds to a second user, different from thefirst user, for updating the value of the characteristic of theindicator to a second value corresponding to the second user, the secondvalue being different from the first value; and means for responding tothe audio user input request using the indicator, wherein the indicatorincludes the updated value of the characteristic.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for controlling electronic devices, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods forcontrolling electronic devices.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 1C is a block diagram illustrating a system and environment forimplementing a digital assistant, in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-60 illustrate exemplary techniques for activating a digitalassistant using gaze information.

FIGS. 7A-7B are flow diagrams illustrating a method for activating adigital assistant using gaze information.

FIGS. 8A-8L illustrate exemplary techniques for providing context tocommands using gaze information.

FIGS. 9A-9B are flow diagrams illustrating a method for providingcontext to commands using gaze information.

FIGS. 10A-10D illustrate exemplary techniques for providing indicationsthat distinguish between different speakers.

FIGS. 11A-11B are flow diagrams illustrating a method for providingindications that distinguish between different speakers.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for controlling electronic devices. For example,eliminating or reducing the need for users to provide tactile or verbalinput to activate a digital assistant enables users to more effectivelycontrol electronic devices. For another example, identifying an externaldevice through the user's gaze eliminates or reduces the need to providecomplex and time-consuming user input to identify such a device. Suchtechniques can reduce the cognitive burden on a user who controlelectronic devices, thereby enhancing productivity. Further, suchtechniques can reduce processor and battery power otherwise wasted onredundant user inputs.

Below, FIGS. 1A-1C, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for controllingelectronic devices. FIGS. 6A-60 illustrate exemplary user interfaces foractivating a digital assistant using gaze information. FIGS. 7A-7B are aflow diagram illustrating methods of activating a digital assistantusing gaze information in accordance with some embodiments. The userinterfaces in FIGS. 6A-60 are used to illustrate the processes describedbelow, including the processes in FIGS. 7A-7B. FIGS. 8A-8L illustrateexemplary user interfaces for providing context to commands using gazeinformation. FIGS. 9A-9B are a flow diagram illustrating methods ofproviding context to commands using gaze information in accordance withsome embodiments. The user interfaces in FIGS. 8A-8L are used toillustrate the processes described below, including the processes inFIGS. 9A-9B. FIGS. 10A-10D illustrate exemplary user interfaces forproviding indications that distinguish between different speakers. FIGS.11A-11B are a flow diagram illustrating methods of providing indicationsthat distinguish between different speakers in accordance with someembodiments. The user interfaces in FIGS. 10A-10D are used to illustratethe processes described below, including the processes in FIGS. 11A-11B.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) containsinformation (e.g., values) that relates to the distance of objects in ascene from a viewpoint (e.g., a camera, an optical sensor, a depthcamera sensor). In one embodiment of a depth map, each depth pixeldefines the position in the viewpoint's Z-axis where its correspondingtwo-dimensional pixel is located. In some embodiments, a depth map iscomposed of pixels wherein each pixel is defined by a value (e.g.,0-255). For example, the “0” value represents pixels that are located atthe most distant place in a “three dimensional” scene and the “255”value represents pixels that are located closest to a viewpoint (e.g., acamera, an optical sensor, a depth camera sensor) in the “threedimensional” scene. In other embodiments, a depth map represents thedistance between an object in a scene and the plane of the viewpoint. Insome embodiments, the depth map includes information about the relativedepth of various features of an object of interest in view of the depthcamera (e.g., the relative depth of eyes, nose, mouth, ears of a user'sface). In some embodiments, the depth map includes information thatenables the device to determine contours of the object of interest in az direction.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multi-touch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 1C illustrates a block diagram of system 2100 according to variousexamples. In some examples, system 2100 implements a digital assistant.The terms “digital assistant,” “virtual assistant,” “intelligentautomated assistant,” or “automatic digital assistant” refer to anyinformation processing system that interprets natural language input inspoken and/or textual form to infer user intent, and performs actionsbased on the inferred user intent. For example, to act on an inferreduser intent, the system performs one or more of the following:identifying a task flow with steps and parameters designed to accomplishthe inferred user intent, inputting specific requirements from theinferred user intent into the task flow; executing the task flow byinvoking programs, methods, services, APIs, or the like; and generatingoutput responses to the user in an audible (e.g., speech) and/or visualform.

Specifically, a digital assistant is capable of accepting a user requestat least partially in the form of a natural language command, request,statement, narrative, and/or inquiry. Typically, the user request seekseither an informational answer or performance of a task by the digitalassistant. A satisfactory response to the user request includes aprovision of the requested informational answer, a performance of therequested task, or a combination of the two. For example, a user asksthe digital assistant a question, such as “Where am I right now?” Basedon the user's current location, the digital assistant answers, “You arein Central Park near the west gate.” The user also requests theperformance of a task, for example, “Please invite my friends to mygirlfriend's birthday party next week.” In response, the digitalassistant can acknowledge the request by saying “Yes, right away,” andthen send a suitable calendar invite on behalf of the user to each ofthe user's friends listed in the user's electronic address book. Duringperformance of a requested task, the digital assistant sometimesinteracts with the user in a continuous dialogue involving multipleexchanges of information over an extended period of time. There arenumerous other ways of interacting with a digital assistant to requestinformation or performance of various tasks. In addition to providingverbal responses and taking programmed actions, the digital assistantalso provides responses in other visual or audio forms, e.g., as text,alerts, music, videos, animations, etc.

As shown in FIG. 1C, in some examples, a digital assistant isimplemented according to a client-server model. The digital assistantincludes client-side portion 2102 (hereafter “DA client 2102”) executedon user device 104 and server-side portion 2106 (hereafter “DA server2106”) executed on server system 2108. DA client 2102 communicates withDA server 2106 through one or more networks 2110. DA client 2102provides client-side functionalities such as user-facing input andoutput processing and communication with DA server 2106. DA server 2106provides server-side functionalities for any number of DA clients 2102each residing on a respective user device 2104.

In some examples, DA server 2106 includes client-facing I/O interface2112, one or more processing modules 2114, data and models 2116, and I/Ointerface to external services 2118. The client-facing I/O interface2112 facilitates the client-facing input and output processing for DAserver 2106. One or more processing modules 2114 utilize data and models2116 to process speech input and determine the user's intent based onnatural language input. Further, one or more processing modules 2114perform task execution based on inferred user intent. In some examples,DA server 2106 communicates with external services 120 throughnetwork(s) 2110 for task completion or information acquisition. I/Ointerface to external services 2118 facilitates such communications.

User device 2104 can be any suitable electronic device. In someexamples, user device 2104 is a portable multifunctional device (e.g.,device 100, described above with reference to FIG. 1A), amultifunctional device or another electronic device (e.g., device 600,800, 1000) A portable multifunctional device is, for example, a mobiletelephone that also contains other functions, such as PDA and/or musicplayer functions. Specific examples of portable multifunction devicesinclude the Apple Watch®, iPhone®, iPod Touch®, and iPad® devices fromApple Inc. of Cupertino, Calif. Other examples of portable multifunctiondevices include, without limitation, earphones/headphones, speakers, andlaptop or tablet computers. Further, in some examples, user device 2104is a non-portable multifunctional device. In particular, user device2104 is a desktop computer, a game console, a speaker, a television, ora television set-top box. In some examples, user device 2104 includes atouch-sensitive surface (e.g., touch screen displays and/or touchpads).Further, user device 2104 optionally includes one or more other physicaluser-interface devices, such as a physical keyboard, a mouse, and/or ajoystick. Various examples of electronic devices, such asmultifunctional devices, are described below in greater detail.

Examples of communication network(s) 2110 include local area networks(LAN) and wide area networks (WAN), e.g., the Internet. Communicationnetwork(s) 2110 is implemented using any known network protocol,including various wired or wireless protocols, such as, for example,Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

Server system 2108 is implemented on one or more standalone dataprocessing apparatus or a distributed network of computers. In someexamples, server system 2108 also employs various virtual devices and/orservices of third-party service providers (e.g., third-party cloudservice providers) to provide the underlying computing resources and/orinfrastructure resources of server system 2108.

In some examples, user device 2104 communicates with DA server 2106 viasecond user device 2122. Second user device 2122 is similar or identicalto user device 2104. User device 2104 is configured to communicativelycouple to second user device 2122 via a direct communication connection,such as Bluetooth, NFC, BTLE, or the like, or via a wired or wirelessnetwork, such as a local Wi-Fi network. In some examples, second userdevice 2122 is configured to act as a proxy between user device 2104 andDA server 2106. For example, DA client 2102 of user device 2104 isconfigured to transmit information (e.g., a user request received atuser device 2104) to DA server 2106 via second user device 2122. DAserver 2106 processes the information and returns relevant data (e.g.,data content responsive to the user request) to user device 2104 viasecond user device 2122.

In some examples, user device 2104 is configured to communicateabbreviated requests for data to second user device 2122 to reduce theamount of information transmitted from user device 2104. Second userdevice 2122 is configured to determine supplemental information to addto the abbreviated request to generate a complete request to transmit toDA server 2106. This system architecture can advantageously allow userdevice 2104 having limited communication capabilities and/or limitedbattery power (e.g., a watch or a similar compact electronic device) toaccess services provided by DA server 2106 by using second user device2122, having greater communication capabilities and/or battery power(e.g., a mobile phone, laptop computer, tablet computer, or the like),as a proxy to DA server 2106. While only two user devices 2104 and 2122are shown in FIG. 1C, it should be appreciated that system 2100, in someexamples, includes any number and type of user devices configured inthis proxy configuration to communicate with DA server system 2106.

Although the digital assistant shown in FIG. 1C includes both aclient-side portion (e.g., DA client 2102) and a server-side portion(e.g., DA server 2106), in some examples, the functions of a digitalassistant are implemented as a standalone application installed on auser device. In addition, the divisions of functionalities between theclient and server portions of the digital assistant can vary indifferent implementations. For instance, in some examples, the DA clientis a thin-client that provides only user-facing input and outputprocessing functions, and delegates all other functionalities of thedigital assistant to a backend server.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,and 1100 (FIGS. 7A-7B, 9A-9B, and 11A-11B). A computer-readable storagemedium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-60 illustrate exemplary user interfaces for activating andinteracting with a digital assistant using glance and voice commands, inaccordance with some embodiments. These figures are used to illustratethe processes described below, including the processes in FIGS. 7A-7B.

FIGS. 6A-6D illustrate user 620 activating an exemplary digitalassistant on electronic device 600 by glancing at electronic device 600.Once the digital assistant becomes activated, user 620 turns on thetable lamp by speaking a command 624A-624B to the digital assistant.

FIG. 6A illustrates a digital assistant on electronic device 600 that isin an inactive state as indicated by display 602 being off. In someembodiments, the digital assistant is in an inactive state whenelectronic device 600 does not detect a user gaze or user 620 looking atelectronic device 600. In some embodiments, the digital assistant is inan inactive state prior to the electronic device 600 detecting a buttonpress (or other activation command) and/or prior to another device(e.g., watch 630) having receiving an activation command andtransmitting an activation instruction to the electronic device. User620 may glance at electronic device 600 to trigger the activation of thedigital assistant when the gaze information based on the gaze of user620 satisfies a set of one or more activation criteria. The electronicdevice 600 obtains gaze information of the gaze of user 620 using one ormore camera sensors optionally located on external devices 616A and/orintegrated with electronic device 600, such as camera 616B. Camerasensors 616A are wirelessly connected to electronic device 600 oralternatively could be wired. The one or more camera sensors includeinfrared camera sensors and/or visible light sensors that measure gazeinformation once a gaze has been detected. The gaze informationoptionally includes one or more of: the position of the user's headposition, the dwell time or the duration of the gaze, the direction ofthe gaze, the field of view 606 of the gaze, and whether an object(e.g., electronic device 600 or an external device such as table lamp618) is within the field of view 606 of the gaze.

Electronic device 600 determines whether the gaze information obtainedfrom the one or more camera sensors 616A-616B satisfies a set of one ormore activation criteria. In other words, electronic device 600determines whether user 620 intended to look at electronic device 600 toactivate the digital assistant. The set of one or more activationcriteria optionally includes a direction criterion that is satisfiedwhen the user's gaze is directed in the direction of electronic device600. The set of one or more activation criteria also optionally includesa dwell time criterion that is satisfied when electronic device 600detects a dwell time or duration of the gaze in the direction ofelectronic device 600 for greater than a non-zero, predetermined periodof time (e.g., a couple seconds). If the dwell time or duration of thegaze is less than the threshold time period, this may indicate that theuser does not intend to trigger the digital assistant. Thus, a dwelltime of less than the threshold time period does not satisfy theactivation criteria, resulting in the digital assistant not beingactivated.

The set of one or more activation criteria also optionally includes afield of view criteria. As illustrated in FIG. 6A, user 620 is notlooking at electronic device 600 and electronic device 600 determinesthat device 600 is not in the field of view 606 of user 620. As furtherdiscussed below, the field of view criterion is satisfied whenelectronic device 600 is determined to be in field of view 606 of user620, but is not satisfied when the electronic device 600 is determinedto not be in the field of view 600 of use 620. Using the field of view606 to determine whether a user 602 is looking at a target electronicdevice (e.g., device 600) results in a higher gaze detection rate as agaze may be detected in the field of view even if the user is notlooking directly at the target electronic device, but still intends toidentify (or activate) the target electronic device.

The field of view 606 is a range of degrees above and below the user'sline-of-sight 612 as indicated by the threshold offset angle 604. Insome embodiments, the field of view criterion is satisfied whenelectronic device 600 is directly in the line-of-sight 612 of user 620,or the determined offset degrees is zero. In some embodiments, a fieldof view criterion is satisfied when a determined offset angle 622 of thegaze is less than the threshold offset angle 604 (e.g., the maximumacceptable deviation from a line-of-sight 612 of user 620 lookingdirectly at the electronic device as illustrated in FIG. 6B). Thedetermined offset angle 622 (in this example) and the threshold offsetangle 604 are greater than zero degrees (e.g., thirty degrees). Thedetermined offset angle 622 is calculated based on the angle formedbetween a line-of-sight 612 from the gaze of user 620 (e.g., where theuser is actually looking) and a calculated line-of-sight 608 from user620 to electronic device 600 (e.g., the ideal path of the user lookingdirectly at electronic device 600). When the offset angle 622 is greaterthan threshold offset angle 604, the field of view criterion is notsatisfied resulting in the digital assistant remaining not activatedbecause electronic device 600 is outside field of view 606, asillustrated in FIG. 6A. In some embodiments, if electronic device 600 isdetermined to be positioned more than a non-zero threshold number ofdegrees (e.g., more than 30 degrees) outside the field of view 606 ofuser 620, electronic device 600 is not in the user's gaze and thedigital assistant is not activated. In some embodiments, line-of-sight612 is measured based on the head position of the user. In someembodiments, the head position of the user is based on the tilt orrotation (e.g., yaw, pitch, and/or roll) of the user's head.

In FIG. 6A, the digital assistant on electronic device 600 is notactivated because the gaze information obtained from the camera sensors(e.g., 616A, 61B) does not satisfy the set of one or more activationcriteria, as discussed above. Electronic device 600 determines that user620 is not looking at electronic device 600 when the dwell time of thegaze of user 620 is less than the threshold dwell time or electronicdevice 600 is not in the field of view of user 620. In some embodiments,the field of view criterion is not satisfied when the determined offsetangle 622 between the user's line-of-sight 612 and a calculatedline-of-sight 608 is greater than the threshold offset angle 604. Whenthe digital assistant is not activated and the gaze information does notsatisfy the set of one or more activation criteria, electronic device600 forgoes activating the digital assistant. When the digital assistantis not activated, the electronic device 600 optionally does not turn onone or more of a microphone or a speaker, does not record audio, and/ordoes not enable processing of recorded audio for the purpose ofperforming a spoken command (e.g., electronic device 600 can stillprocess audio to detect trigger words, but does not process the audiofor performance of non-activation commands). In some embodiments,electronic device 600 does not provide any indications using a visual oraudio indicator when the digital assistant is not activated (e.g., thestate of electronic device 600 remains unchanged). In some embodiments,electronic device 600 remains in the same inactive state that it was inprior to the determination that the gaze information has not satisfiedthe set of one or more activation criteria.

In FIG. 6A, user 620 starts speaking a portion 624A “Turn . . . ” ofcommand 624A-624B “Turn on the table lamp” before the digital assistantis activated. In some embodiments, portion 624A of command 624A-624B isnot processed, is cancelled, and/or is ignored by the digital assistantif the digital assistant is not subsequently activated (e.g., within aset (non-zero) duration of time), as further discussed below. In someembodiments, portion 624A of command 624A-624B received by electronicdevice 600 prior to the digital assistant being activated is processedif the digital assistant is activated (e.g., by user 620 looking atelectronic device 600, satisfying the set of one or more activationcriteria) prior to completing command 624A-624B (or within the setduration of time), as further discussed below.

As illustrated in FIG. 6B, user 620 is looking at electronic device 600and electronic device 600 determines that electronic device 600 is inthe field of view 606 of user 620. The gaze information, obtained fromthe camera sensors (e.g., 616A, 616B), satisfies the set of one or moreactivation criteria.

In FIG. 6C, electronic device 600 determines that the gaze information,obtained from the camera sensors (e.g., 616A, 616B), satisfies the setof one or more activation criteria and, in response, activates thedigital assistant. Activating the digital assistant optionally includesone or more of: turning on a microphone or speaker, recording audio, andenabling processing of recorded audio for the purpose of performing aspoken command (rather than merely detecting a trigger phrase).Electronic device 600 optionally provides an indication (e.g., viaindicator 610A, 610B, or 610C) that the set of one or more activationcriteria has been satisfied and/or that the digital assistant has beenactivated. The indicator is optionally a visual indication 610A, anaudio indication 610B, the digital assistant speaking a confirmation610C, or any combination of the different indicators. Providing visualindication 610A optionally includes one or more of: turning on display602 of electronic device 600, turning on an LED of electronic device600, displaying a light of a particular color (e.g., blue or a colorother than the default color when the digital assistant is notactivated), a light pattern, or a visual output on display 602 ofelectronic device 600. In some embodiments, visual indicator 610Aindicating that the digital assistant is activated is different from thevisual indicator 610A indicating when the digital assistant hasperformed a command or is in an inactive state. For example, theelectronic device displays a first color for visual indictor 610A inresponse to the set of one or more activation conditions being met,displays as second color for visual indicator 610A in response to thedigital assistant being activated, displays a third color for visualindicator 610A in response to a determination that the digital assistanthas performed a command, and/or displays a fourth color for visualindicator 610A in response to changing the digital assistant to not beactivated. An audio indication 610B optionally includes one or more of:playing a sound, phrase, word, or tone. In some embodiments, audioindicator 610B indicating that the digital assistant is activated (orthat the set of one or more activation criteria has been met) isdifferent from audio indicator 610B indicating when the digitalassistant has performed a command (e.g., 624A) or is in an inactivestate. The digital assistant optionally provides a digital assistantvoice confirmation 610C (e.g., “How can I help you?”) indicating thatthe digital assistant has been activated or that the set of one or moreactivation criteria has been met. In some examples, as described infurther detail with respect to FIGS. 10A-10D, the electronic deviceoutputs the voice confirmation using a particular voice (e.g., accent,male or female voice) based on the detected user.

In FIG. 6C, subsequent to the electronic device activating the digitalassistant and providing indication(s) using display 602, the electronicdevice detects user 620 finishing speaking the remaining portion 624B “. . . on the table lamp” of command 624C “Turn on the table lamp,”. Insome embodiments, the electronic device 600 detects user 620 speakingthe entire command 624C “turn on the table lamp” after the digitalassistant is activated. Optionally, electronic device 600 providesindication 610C in accordance with a determination that the set of oneor more activation criteria is met prior to beginning to receive command624A-624B and electronic device 600 does not provide indication 610C inaccordance with a determination that the set of one or more activationcriteria is met after (but not prior) to beginning to receive command624A-624B.

In some embodiments, the electronic device 600 is producing an audiooutput, such as playing music, at a first volume prior to receiving theremaining portion 624B of command 624A-624B. In some embodiments, inresponse to electronic device 600 receiving first portion 624A ofcommand 624A-624B, electronic device 600 reduces (ducks) the firstvolume of the audio output to a second volume that is lower than thefirst volume, where the second volume is optionally based on thedistance between user 620 and electronic device 600. The first volume ofthe audio output is lowered so that electronic device 600 may betterdetect the words with reduced interference of background noise. In someembodiments, the first volume is reduced in response to thedetermination that the set of one or more activation criteria is met. Insome embodiments, the amount of volume reduction is based on thedistance between user 620 and electronic device 600 at the time firstportion 624A of command 624A-624B is received (and not second portion624B). Electronic device 600 determines the distance between user 620and electronic device 600 using the external camera sensors 616A and/orthe camera sensors 616B on electronic device 600. In some embodiments,electronic device 600 variably reduces the volume of the audio output bymuting or lowering the volume of the audio output while detecting thatuser 620 is speaking. Electronic device 600 restores the volume of theaudio output back to the first volume after detecting the end of command624B. The volume change is not based on the content of the request. Insome embodiments, even though electronic device 600 detects user 620speaking the first portion 624A of command 624A-624B prior to activatingthe digital assistant, the digital assistant is still able to processthe command (including 624A) if a set of one or more performancecriteria is met. When the set of one or more performance criteria ismet, the digital assistant performs the command based on the content ofthe request. The set of one or more performance criteria optionallyincludes one or more of: a command completion criterion, an actionablecriterion, and an activation criteria. The command completion criterionis met when electronic device 600 detects the end of a received audiocommand (e.g., audio user input request). The end of command 624A-24B isdetermined by electronic device 600 detecting a pause in received audio(or lack of receiving user audio) for more than a non-zero,predetermined period of time. In some embodiments, the commandcompletion criterion is not met when the detected pause is for less thana non-zero, predetermined period of time (e.g., the user is not donespeaking the command). An actionable criterion is met when electronicdevice 600 determines that the received command is actionable (e.g.,that the device has authority and/or capability to perform the command).In some examples, if the command is to access information from anaccount, but the electronic device has not received authorization toaccess the account, then the command is not actionable because thedevice does not have authority to access the account. In some examples,the actionable criterion is not met when electronic device 600 is unableto process the received request into a command that the digitalassistant can perform or transmit (e.g., command is to “turn on the tv”,but there is no tv in the room to which the corresponding instructioncould be sent). The activation criteria is met when the digitalassistant has been activated.

FIG. 6D illustrates that once the set of one or more performancecriteria is met while the digital assistant is activated, the digitalassistant performs the command. If the digital assistant successfullyprocesses the command and determines that the performance criteria aremet, the digital assistant will send an instruction to cause a change instate of an appropriate device. In this example, the instruction is sentto table lamp 618 (an external device) to turn on. In some embodiments,the determination as to which external device to act on is made inaccordance with the description of FIGS. 8A-8C, as described in greaterdetail below. After the digital assistant has performed the command,electronic device 600 optionally provides an indicator (e.g., indicator610A, 610B, 610C) indicating whether command 624A-624B has beensuccessfully performed. In some embodiments, the indicator is a visualindicator 610A that displays a light of a particular color (e.g., blueor a color other than the default color when the digital assistant isnot activated) or a light pattern to indicate that the digital assistanthas performed command 624A-624B. In some embodiments, the indicator isan audio indicator 610B that plays a sound, phrase, word, or tone. Insome embodiments, the indicator is a confirmation 610C spoken by thedigital assistant, which can speak in a particular voice (e.g., accent,male or female voice), such as described with respect to FIGS. 10A-10D,when the digital assistant has performed command 624A-624B. In someembodiments, user 620 may customize the visual, audio, or digitalassistant indicators to include values of characteristics (e.g., a username, particular user preferences for light color, pattern, sound,voice, accent) associated with his/her profile as discussed below withrespect to FIGS. 10A-10D. For example, in FIG. 6D, the digital assistantmay provide a confirmation, “Jack, the table lamp has been turned on.”The name of user 620, is obtained from the user profile of user 620,which user 620 provided during registration, and is determined asdiscussed below with respect to FIGS. 10A-10D. The registration processis described in detail below with respect to FIGS. 10A-10D and withrespect to method 1100. The digital assistant may utilize settings fromuser 620's profile to further customize the indicator to reflect whichuser (e.g., Jack) has spoken the command

When the set of one or more performance criteria is not met, electronicdevice 600 forgoes performing the command based on the content of thecommand. In some examples, the set of one or more performance criteriais not met when the actionable criterion is not met. When the actionablecriterion is not met, electronic device 600 optionally produces aheadshake indication as illustrated in FIG. 6O, to indicate that thedigital assistant is unable to perform the command because it could notprocess the command, lacks authorization, or is incapable of performingthe command. The headshake indication in FIG. 6O comprises a display oflights or a pattern of lights 602A on a first side of the display 602 ofelectronic device 600 (as shown in 6O-A), followed by a pattern oflights 602B on a second side of the display 602 (as shown in 6O-B),followed by the pattern of lights 602A on the first side of the display602 (as shown in 6O-C), which simulates a person shaking his/her head.In some embodiments, a particular indicator (e.g., pattern of light,color, or particular sound) is produced by electronic device 600 whenthe performance criteria is not met. The particular indicator maycorrespond to a particular error code that indicates why the digitalassistant was unable to perform the command (e.g., blue light indicatesthe command was not understood, purple light indicates lack ofauthorization). In some embodiments, the indicator produced when thedigital assistant is unable to perform the command is different than theindicator produced when the digital assistant is able to perform thecommand.

FIGS. 6E-6G illustrate another embodiment where user 620 activates adigital assistant on a wearable or mobile electronic device 630. In FIG.6E, the digital assistant on electronic device 630 is activated whenelectronic device 630 detects a user input or gesture such as a wristraise. In some embodiments, user 620 may also optionally press a button,rotate a crown, or provide audio user input to activate the digitalassistant on electronic device 630. Once the digital assistant isactivated, electronic device 630 optionally provides a visual indictor610A (e.g., light), audio indicator 610B (e.g., a sound, tone, word), ordigital assistant voice confirmation 610C to indicate that the digitalassistant has been activated or that the set of one or more activationcriteria are met. The various types of indicators are discussed abovewith respect to FIG. 6B.

In FIG. 6F, electronic device 630 detects a spoken command comprisingcommand 624C “Turn on the table lamp” from user 620. After receiving thespoken command, the digital assistant determines whether a set of one ormore performance criteria (e.g., an actionable criterion, a commandcompletion criterion, an activation criterion) are met. As discussedabove, when one or more performance criteria is met, the digitalassistant performs the command based on the content of the audio inputrequest. As illustrated in FIG. 6F, the electronic device optionallyalso determines whether the user's gaze satisfies a set of one or moregaze criteria to identify an external device upon which to act. The setof one or more gaze criteria are described in further detail, below.

FIG. 6G illustrates electronic device 630 providing an indicator (e.g.,610A, 610B, 610C) that the command was successfully performed in causingthe table lamp to turn on from an off state. The indicators displayedupon the successful performance of the command are discussed above withrespect to FIG. 6E.

FIGS. 6H-6J illustrate when the digital assistant does not perform thecommand associated with the spoken command 624A-624B when the set of oneor more performance criteria is not met because user 620 has brokenhis/her gaze while speaking command 642A-624B. The set of one or moreperformance criteria includes a continuous gaze criterion that is metwhen electronic device 600 determines that second gaze information(e.g., obtained by electronic device 600 using the one or more camerasensors 616A, 616B (while user 620 is speaking) indicates that user 620did not break his/her gaze directed at electronic device 600 for morethan a threshold duration between the activation of the digitalassistant and the completion of speaking command 624A-624B. In someembodiments, the threshold duration is zero, meaning the user cannotbreak his/her gaze while speaking. In some embodiments, the thresholdduration is a non-zero time period, which allows the user to brieflylook away without cancelling the command.

In FIG. 6H-6I, user 602 breaks his/her gaze directed at electronicdevice 600 while speaking command 624A-624B to “turn on the table lamp”while electronic device 600 is activated. As illustrated in FIG. 6H, theelectronic device 600 determines that the user 620 is looking at theelectronic device while electronic device 600 receives a first portion624A of command 624A-624B “turn . . . ”. In FIG. 6I, electronic device600 detects a break in the user gaze when user 620 turns 180 degrees tolook away from electronic device 600 before having finished speaking theremainder 624B of command 624A-624B “ . . . on the table lamp.” Theuser's gaze is broken from electronic device 600 when electronic device600 determines that the field of view criterion is not satisfied formore than a non-zero, threshold duration (e.g., 3 seconds).

FIG. 6J illustrates that electronic device 600 forgoes performingcommand 624A-624B to “turn on that light” when the continuous gazecriterion is not met, even when the set of one or more activationcriteria has been met (e.g., in FIG. 6H). As a result, table lamp 618remains off because the digital assistant has not transmitted theinstructions to table lamp 618 to turn on. Electronic device 600optionally produces an indicator (e.g., 610A, 610B, 610C) that indicatesthat the command has not been performed. In some embodiments, theindicator may be a visual indicator 610A (e.g., colored light or lightpattern), an audio indicator 610B (e.g., sound, speech, or a particularvoice), or a digital voice confirmation 620C, as discussed above. Theindicator (e.g., 610A, 610B, 610C) provided by the electronic device 600when command 624A-624B is not performed is optionally different than theindicator (e.g., 610A, 610B, 610C) provided by electronic device 600when command 624A-624B is successfully performed.

FIGS. 6K-6N illustrate that even if electronic device 600 detects thatuser 620 breaks his/her gaze directed at electronic device 600 whileelectronic device receives command 624D-624F (when electronic device 600is activated), the continuous gaze criterion is still satisfied if thebreak in the gaze is less than the threshold duration. FIG. 6Killustrates that electronic device 600 has activated the digitalassistant and is receiving portion 624D “turn . . . ” of command624D-624F to “turn on the table lamp” from user 620. In FIG. 6L,electronic device 600 continues to receive second portion 624E “ . . .on the . . . ” of command 624D-624F from user 620, but electronic device600 detects a break in the user's gaze when the user looks away fromelectronic device 600.

In FIG. 6M, electronic device 600 detects that user 620 has returned hisgaze back to electronic device 600 within the threshold duration (e.g.,3 seconds). The electronic device continues to receive last portion 624F“ . . . table lamp” of command 624D-624F. Because the break in gaze isfor less than the threshold duration, the continuous gaze criterion isstill satisfied. In FIG. 6N, when the continuous gaze criterion issatisfied, the digital assistant performs command 624D-624F to “turn onthe table lamp” and provides an indication (e.g., visual 610A, audio610B, and digital assistant confirmation 610C indications) once tablelamp 618 has turned on.

FIGS. 7A-7B are flow diagrams illustrating a method for 700 using anelectronic device in accordance with some embodiments. Method 700 isperformed at an electronic device (e.g., 100, 300, 500, 600, 630, 800,1000). Some operations in method 700 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 700 provides an intuitive way for activatinga digital assistant on an electronic device by glancing at theelectronic device. The method reduces the cognitive burden on a userwhen providing user input (e.g., audio input by speaking or touch inputvia button presses) to activate the digital assistant. In somecircumstances, the user is unable to effectively use voice activation(e.g., when the room is noisy) or provide tactile user input (e.g.,pressing a button). Therefore, by being able to activate the digitalassistant by looking at the electronic device, the user is able tointeract with the digital assistant using a more efficient user-deviceinterface.

While a digital assistant of the electronic device (e.g., 600) is notactivated (702), the electronic device (e.g., 600) obtains (704), usingone or more camera sensors (e.g., cameras 616A, 616B), first gazeinformation (e.g., of the user 620). For example, the one or more camerasensors are infrared camera sensor(s) and/or visible light sensor(s).For example, the one or more camera sensors are external to theelectronic device (e.g., 600), such as by being wirelessly connected tothe electronic device.

In accordance with a determination (706) (e.g., while the digitalassistant is not activated) that the first gaze information satisfies aset of one or more activation criteria: (e.g., the angle of the gaze isless than a threshold number of degrees relative to a line-of-sight, thegaze is in a particular direction, the duration of the gaze is greaterthan or equal to a predetermined period of time), the electronic device(e.g., 600) activates (708) the digital assistant of the electronicdevice (e.g., 600) (e.g., by turning on a microphone, enablingprocessing of recorded audio).

Using gaze detection to activate the digital assistant when the set ofone or more activation criteria is satisfied provides the user with amore efficient user interface for activating a digital assistant,particularly in contexts where the user cannot press a button or usevoice controls because the room is too noisy. Providing improved userinterfaces to activate the digital assistant without requiring tactileuser input (e.g., a button press) or voice input enhances theoperability of the digital assistant and makes the user interface of thedigital assistant interface more efficient. In addition, using gazedetection reduces the number of user inputs needed to activate thedigital assistant to perform commands, which enhances the operability ofthe electronic device.

In some embodiments, the set of one or more activation criteria includesa field of view criterion that is met when a determined offset angle(e.g., 622) is less than a threshold offset angle (e.g., 604) (e.g., anon-zero degrees value, the maximum acceptable deviation from the userlooking directly at the device), wherein the determined offset angle(e.g., 622) is an angle formed between: a line-of-sight (e.g., 612)(e.g., determined from the gaze information) of a gaze of a user (e.g.,620) and a calculated line-of-sight (e.g., 608) from the user (e.g.,620) to the electronic device (e.g., 600).

Using a field of view criterion as an activation criteria allows theuser's gaze to be detected without requiring the user (e.g., 620) tolook directly at the electronic device (e.g., 600). Instead, as long asthe electronic device (e.g., 600) is within a field of view (e.g., 606)of the user's gaze, the user's gaze satisfies the activation criteria,allowing the digital assistant to be activated. Using the field of viewcriterion allows the digital assistant to be activated via gaze moresuccessfully, which enhances the operability of the digital assistantand makes the gaze detection more efficient (e.g., the digital assistanthas a higher activation rate since the electronic device (e.g., 600)does not have to be in the direct line-of-sight (e.g., 612) of the user(e.g., 620)).

In some examples, if the electronic device (e.g., 600) is determined tobe positioned more than a threshold number of degrees (e.g., outside thefield of view 606 of the gaze), the electronic device (e.g., 600) is notin the user's gaze and the digital assistant is not activated. In someexamples, when the electronic device (e.g., 600) is in the field of view(e.g., 606) of the gaze by being within the threshold number of degrees,the digital assistant is activated.

In some embodiments, the line-of-sight (e.g., 612) of the gaze of theuser (e.g., 620) is based on a head position of the user (e.g., 620). Insome examples, the user's head position may be affected by the tilt orrotation (e.g., yaw, pitch, and roll of the user's head).

In some embodiments, the set of one or more activation criteria includesa dwell time criterion that is satisfied when a dwell time (e.g.,duration) of the gaze determined from the first gaze information is morethan a threshold period of time (e.g., a non-zero threshold period oftime). In some examples, if the dwell time of the gaze is less than athreshold time period, the digital assistant is not activated.

Further in accordance with the determination (706) that the first gazeinformation satisfies the set of one or more activation criteria, theelectronic device (e.g., 600) provides (710) an indication that the setof one or more activation criteria has been satisfied and/or that thedigital assistant of the electronic device is in transition ortransitioning into being activated.

Providing an indication (e.g., 610A, 610B, 610C) that the set of one ormore activation criteria has been satisfied and that the digitalassistant is activated provides the user with feedback about the currentstate of the digital assistant. The indication (e.g., 610A, 610B, 610C)can be visual, audio, or a digital assistant voice confirmation, whichprovides customizable feedback for various contexts. For example, incontexts where a sound indicator cannot be heard (e.g., a noisy room),providing visual feedback (e.g., 610A) allows the user (e.g., 620) toknow whether the digital assistant is activated and can processcommands. Providing customized feedback of the state of the digitaldevice enhances the operability of the digital assistant and makes theuser-device interface more efficient (e.g., the user (e.g., 620) doesn'tissue commands when the digital assistant is not active) by informingthe user (e.g., 620) when the digital assistant is available to processcommands (e.g., activated) and when it is unavailable (e.g., inactive).Further, the feedback of the state of the digital assistant allows theuser (e.g., 620) to use the digital assistant more efficiently.

In some embodiments, the indication (712) is a visual indication (e.g.,610A) (such as the electronic device 600 turning on a display, LED, orlight of the electronic device) that indicates that the digitalassistant is activated. In some embodiments, the indication (714) is anaudio indication (e.g., 610B) (such as electronic device 600 playing asound through a speaker of the electronic device 600) to indicate thatthe digital assistant is now activated.

In some embodiments, in accordance with a determination (716) (e.g.,while the digital assistant is not activated) that the first gazeinformation does not satisfy the set of one or more activation criteria:(e.g., electronic device (e.g., 600) is not in the user's field of view(e.g., 606), the gaze is in the wrong direction, the duration of thegaze is less than a predetermined period of time), the electronic device(e.g., 600) forgoes activating the digital assistant. In someembodiments, forgoing activating the digital assistant includes thedigital assistant remaining not activated or the electronic device(e.g., 600) not enabling the microphone or processing of recorded audio.In some examples, when the first set of gaze information does notsatisfy the set of one or more activation criteria, the electronicdevice (e.g., 600) also forgoes providing the indicator (e.g., 610A,610B, 610C) that the set of one or more activation criteria has beensatisfied.

In some embodiments, the electronic device (e.g., 600) receives (718) anaudio user input request to perform a command (e.g., 624A-624B, 624C).In response to the electronic device (e.g., 600) receiving (720) theaudio user input request to perform the command (e.g., 624A-624B, 624C)(or in accordance with the digital assistant interpreting the command(e.g., 624A-624B, 624C)) and in accordance with a determination that aset of one or more performance criteria (e.g., an actionable criterion,a command completion criterion, an activation criterion) is met, theelectronic device (e.g., 600) performs (722) the command (e.g.,624A-624B, 624C) based on a content of the audio user input request. Insome examples, in response to receiving the audio input request and inaccordance with a failure to interpret the command (e.g., 624A-624B,624C), the electronic device (e.g., 600) forgoes performing the command(e.g., 624A-624B, 624C) and provides an indication (e.g., 610A, 610B,610C) (e.g., a display of a visual indication, such as a headshakeindication) that the electronic device (e.g., 600) did not interpret thecommand (e.g., 624A-624B, 624C). Thus, the electronic device (e.g., 600)provides an indication (e.g., 610A, 610B, 610C) if the digital assistantdoesn't understand the audio input. In some examples, when the digitalassistant is not activated, the digital assistant forgoes performing thereceived command (e.g., 624A-624B, 624C).

In some embodiments, in response to the electronic device (e.g., 600)receiving the audio user input request to perform the command (e.g.,624A-624B, 624C) and in accordance with a determination that the set ofone or more performance criteria is not met (e.g., actionable criterion,command completion criterion, activation criterion), the electronicdevice (e.g., 600) provides a headshake indication. The headshakeindication includes the electronic device (e.g., 600) displaying a firstpattern of lights on a first side of a display (e.g., 602) of theelectronic device (e.g., 600). Subsequent to displaying the firstpattern of lights, the electronic device (e.g., 600) displays a secondpattern of lights on a second side of the display (e.g., 602) of theelectronic device (e.g., 600). Subsequent to displaying the secondpattern of lights, the electronic device (e.g., 600) displays the firstpattern of lights on the first side of the display (e.g., 602) of theelectronic device (e.g., 600).

Providing a visual indication (e.g., 610A) (e.g., a headshake indication(e.g., 602A-602B)) that the set of one or more performance criteria isnot met provides the user with feedback that the command issued by theuser is unable to be processed. Providing a customizable indication,such as the headshake indication (e.g., 602A-602B), that indicates whenthe command (e.g., 624A-624B, 624C) will not be processed enhances theoperability of the digital assistant and makes the user-device interfacemore efficient by informing the user (e.g., 602) that the command (e.g.,624A-624B, 624C) will not be performed. In addition, customizedindications (e.g., 610A, 610B, 610C) corresponding to error codesprovide improved feedback to the user which communicates why the command(e.g., 624A-624B, 624C) was not carried out, which makes the user-deviceinterface more efficient.

In some embodiments, the set of one or more performance criteriaincludes a completion criterion that is met when the electronic device(e.g., 600) detects the end of a received audio command (e.g., the endof the audio user input request, a pause of audio for more than apredetermined period of time). In some examples, the set of one or moreperformance criteria includes a actionable criterion that is met whenthe electronic device (e.g., 600) determines that the received commandis actionable (e.g., that the digital assistant has authority and/orcapability to perform the command).

In some embodiments, the electronic device (e.g., 600) starts receivingthe audio user input request while the digital assistant is notactivated. In some examples, the digital assistant is inactive becausethe gaze information does not yet satisfy the set of one or moreactivation conditions. This may happen, for example, when the user(e.g., 620) begins speaking the command (e.g., 624A-624B, 624C) beforelooking at the digital assistant. In some examples, first gazeinformation satisfies the set of one or more activation criteria and, inresponse, the digital assistant is activated before the electronicdevice (e.g., 600) finishes receiving the audio user input request toperform the command.

Being able to receiving the audio user input request before the digitalassistant is activated allows the user (e.g., 602) to begin speakingeven if the user (e.g., 602) hasn't activated the digital assistant yet.Detecting the audio user input request when the set of activationconditions has not yet been met enhances the operability of the digitalassistant and makes the device-user interface more efficient because theactivation and speaking of a command (e.g., 624A-624B, 624C) do not haveto be performed in order.

In some embodiments, in response to the electronic device (e.g., 600)receiving the audio user input request to perform the command (e.g.,124C) and in accordance with a determination that the set of one or moreperformance criteria is not met (e.g., various criteria that should bemet for the electronic device (e.g., 600) to perform the command (e.g.,624A-624B, 624C)), the electronic device (e.g., 600) forgoes (724)performing the command (e.g., 624A-624B, 624C) based on the content ofthe audio user input request, wherein the set of one or more performancecriteria includes a continuous gaze criterion that is met when theelectronic device (e.g., 600) determines that second gaze information(e.g., obtained by the electronic device using the one or more camerasensors) indicates that the user (e.g., 602) does not break a gazedirected at the electronic device (e.g., 600) for more than a thresholdduration (e.g., a non-zero duration) between activation of the digitalassistant and the completion of the audio user input request. In someexamples, the digital assistant does not perform the command (e.g.,624A-624B, 624C) because the user (e.g., 602) breaks their gaze with thedevice (e.g., user (e.g., 602) looked away before completion of thecommand, user (e.g., 602) looked away for more than 1 second at a time).In some examples, the threshold duration is 0 seconds. In some examples,the threshold duration is a duration that is non-zero (e.g., 0.5seconds).

In some embodiments, the electronic device (e.g., 600) produces an audiooutput (e.g., the electronic device (e.g., 600) is playing a song),wherein the audio output is being produced at a first volume prior toreceiving the audio user input request. In response to beginning toreceive the audio user input request, the electronic device (e.g., 600)reduces a volume of the audio output to a second volume that is lowerthan the first volume, wherein the second volume is based on a distancebetween a user (e.g., the user providing the audio user input request)and the electronic device (e.g., 600). In some examples, the electronicdevice (e.g., 600) determines a distance between a user (e.g., 602) andthe electronic device (e.g., 600) using the external sensors (e.g.,616A) or the sensor (e.g., 616B) on the electronic device (e.g., 600)and determines whether to mute or reduce the volume of the music whilethe user (e.g., 602) is talking (e.g., variably duck the audio output).In some examples, the electronic device may bring the volume back up tothe first volume after detecting the end of the command (e.g., 624C). Insome examples, the volume change is not based on the content of therequest.

Reducing the audio output volume or muting the audio output when theelectronic device receives an audio user input request enables the audiouser input request to be more easily processed and results in a higherlikelihood that the command (e.g., 624C) derived from the audio userinput request will be understood by the electronic device as ambientnoise is reduced. Removing possible ambient noise or sounds that couldinterfere with the command (e.g., 624C) that is processed by the digitalassistant enhances the operability of the digital assistant and makesthe user-device interface more efficient by enabling a higher accuracyof executing the correct command, which improves the user experience asthe user (e.g., 602) doesn't have to repeat the command again when thedigital assistant is unable to process the command (e.g., 624C).

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below. For example, method 700 mayinclude one or more of the characteristics of the various methodsdescribed below with reference to the processes in FIGS. 9A, 9B, 11A,and 11B. For brevity, these details are not repeated below.

It should be understood that the particular order in which theoperations in the following FIGS. 9A-9B and 11A-11B have been describedis exemplary and not intended to indicate that the described order isthe only order in which the operations could be performed. One ofordinary skill in the art would recognize various ways to reorder theoperations described herein, as well as excluding certain operations.For brevity, these details are not repeated here. Additionally, itshould be noted that aspects of the methods and processes describedthroughout this description may be incorporated with one another.

FIGS. 8A-8L illustrate exemplary user interfaces for the electronicdevice to use gaze information to determine the context (e.g., anappliance that the command is directed at) for performing a command oncethe digital assistant has been activated, in accordance with someembodiments. The techniques illustrated in FIGS. 8A-8L optionally workin conjunction with or include the techniques illustrated in FIGS.6A-60, which disclose how the user may activate the digital assistant bylooking at the electronic device and issuing commands. Thus, thetechniques described below include one or more of the characteristics ofthe various techniques described above with reference to FIGS. 6A-60 andmethod 700. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 9A-9B.

FIGS. 8A-8C illustrate electronic device 800 receiving an audio userinput request from user 820 to perform a first command 824A-824B oncethe digital assistant of electronic device 800 has been activated. Thedigital assistant is activated based on a trigger word, a gaze (e.g., asdiscussed above with respect to FIGS. 6A-60), a button press, a wristraise (FIG. 6E-6G) while the user is wearing a wearable electronicdevice (e.g., a watch), and/or detecting an external device (e.g., aphone) being pointed at the electronic device 800. The electronic device(e.g., 800) optionally provides a visual or audio indication 810A-810Bto indicate that the digital assistant is activated.

In FIG. 8A, user 820 is standing in a room with a table lamp 818 and afloor lamp 814. The digital assistant of electronic device 800 has beenactivated based on the electronic device 800 determining that the set ofone or more activation criteria have been satisfied with respect tomethod 700 as discussed above (e.g., device 800 determines that user 820is looking at device 800). Once the digital assistant is activated, theelectronic device detects user 820 speaking a portion 824A “turn . . . ”of the full command 824A-824B. In some embodiments, the complete command824A-824B is applicable to the multiple external devices (e.g., tablelamp 818, floor lamp 814) that may be in the room. In some embodiments,the user's command 824A-824B does not include enough detail for thedigital assistant to determine which external device (e.g., table lamp818, floor lamp 814) the command 824A-824B is directed to. Therefore,based on the command 824A-824B alone, the electronic device 800 isunable to determine whether “that light” refers to table lamp 818 orfloor lap 814.

In FIG. 8B, user 820 indicates which external device (e.g., light)he/she wants to act on (e.g., turn on) by looking at table lamp 818,while finishing the remaining portion 824B “ . . . on that light” ofcommand 824A-824B “turn on that light.” The electronic device receivesand uses gaze information based on the user's gaze, while the user 820is speaking, to determine that table lamp 818 is the intended device,when the user's gaze satisfies a set of one or more gaze criteria.Electronic device 800 obtains information relating to the user's gazethrough the one or more camera sensors that may be located on externaldevices 816A and/or is integrated with electronic device 800 at camera816B. Cameras 816A are wirelessly connected to electronic device 600,though they could alternatively be wired. The one or more camera sensorsinclude infrared camera sensors and/or visible light sensors and measuregaze information once a gaze has been detected. The gaze informationoptionally includes one or more of: the position of the user's headposition, the dwell time or duration of the gaze, the direction of thegaze, the field of view 806 of the gaze, the direction of the gaze, andwhether an object (e.g., electronic device 800 or an external device(e.g., lamps 814, 818) is within the field of view 806 of the gaze(e.g., external device is within a threshold offset angle 804 from auser's line-of-sight 812).

In some embodiments, electronic device 800 determines that the set ofone or more gaze criteria is met when a direction criterion, a dwelltime criterion, and/or a field of view criterion is met. The set of oneor more gaze criteria optionally includes a direction criterion that issatisfied when the gaze is directed in the direction of table lamp 818.

The set of one or more gaze criteria optionally includes a dwell timecriterion that is satisfied when electronic device 800 detects a dwelltime or duration of the gaze in the direction of table lamp 818 forgreater than a non-zero, predetermined period of time (e.g., twoseconds, a threshold time period). In some examples, electronic device800 utilizes the dwell time to determine whether user 820 is looking attable lamp 818 in order to determine which external object to act upon(e.g., to send the instruction to). If the dwell time or duration of thegaze is too short or less than the threshold time period, this indicatesthat the user does not intend the particular external device (e.g.,table lamp 818) to be the target device of the command 824A-824B. Insome embodiments, a dwell time less than the threshold time period doesnot satisfy the gaze criteria, resulting in the command 824A-824B notbeing transmitted to the particular external device identified byelectronic device 800. In some embodiments, a dwell time less than thethreshold time period results in electronic device 800 not identifyingany external device.

The set of one or more gaze criteria optionally includes a field of viewcriterion. The field of view criterion is satisfied for a particularexternal device when an external device, such as table lamp 818, isdetermined to be in field of view 806 of user 820. Table lamp 818 isdetermined to be in field of view 806 of user 820 when table lamp 818 iswithin a threshold offset angle 804 from a user's line-of-sight 812.Using the field of view to determine whether a user is looking at atarget external device (e.g., table lamp 818, floor lamp 814) results ina higher gaze detection rate as a gaze may be detected in the field ofview even if the user is not looking directly at the target device. Insome embodiments, the field of view criterion is satisfied for tablelamp 818 when table lamp 818 is directly in the line-of-sight 812 ofuser 820. In some embodiments, the field of view criterion is satisfiedfor a particular external device when a determined offset angle of thegaze is less than the threshold offset angle 804 to the external device(e.g., the maximum acceptable deviation from a line-of-sight 812 of user820 looking directly at table lamp 818). The threshold offset angle 804is greater than zero degrees (e.g., thirty degrees). The determinedoffset angle is calculated based on the angle formed between aline-of-sight 812 from a gaze of user 820 and a calculated line-of-sightfrom user 820 to electronic device 800. In the example of FIG. 8B, user820 is looking directly at table lamp 818. In some examples, when tablelamp 818 is in the field of view of the gaze by being within thethreshold number of degrees from the user's direct line-of-sight, thefield of view criterion is met for table lamp 818 and electronic device800 optionally transmits the instructions to table lamp 818. When theoffset angle is greater than threshold offset angle 804, the field ofview criterion is not satisfied resulting in the digital assistant nottransmitting the instructions to table lamp 818, which is outside thefield of view 806 of user 820. In some embodiments, if table lamp 818 isdetermined to be positioned more than a threshold number of degreesoutside the field of view 808 of user 820, table lamp 818 is determinedto not be in the user's gaze and electronic device 800 does not transmitthe instructions to table lamp 818. In some embodiments, line-of-sight812 is measured based on the head position of the user. In someembodiments, the head position of the user is based on the tilt orrotation (e.g., yaw, pitch, and/or roll) of the user's head. Aspects ofthese techniques are illustrated and described in further detail abovewith respect to FIGS. 6B-6C.

Electronic device 800 optionally provides an indication (e.g.,indicators 810A, 810B, 810C) when the set of one or more gaze criteriais met for table lamp 818. The indication optionally indicates that thecommand 824A-824B from the received audio user input request isassociated with or is directed to the table lamp 818. The indication maybe a visual 810A or audio 810B indicator that indicates that the digitalassistant has identified table lamp 818 based on the user's gaze. Insome embodiments, the indicator is a visual indicator 810A that displaysa light of a particular color (e.g., blue or a color other than thedefault color when table lamp 818 is identified) or a light pattern toindicate that the digital assistant has identified table lamp 818 basedon the user's gaze. In some embodiments, the indicator is an audioindicator 810B that plays a sound, word, tone, or speaks in a particularvoice (e.g., accent, male or female voice) when the digital assistanthas identified table lamp 818. In some embodiments, the digitalassistant provides an audio confirmation (“turning on the table lamp”)to indicate that electronic device 800 has identified the externaldevice to act on (e.g., to turn on).

In FIG. 8C, when the electronic device determines that the set of one ormore gaze criteria is met for table lamp 818, the digital assistanttransmits instructions to act on the command. For example, theelectronic device determines that the command is to perform a function“turn on” and that the function should be directed at a particulardevice—the table lamp 818. Accordingly, the electronic device transmitsan instruction (e.g., to table lamp 818 or to another device thatcontrols table lamp 818) to turn the table light from an off state to anon state. In some embodiments, the digital assistant transmitsinstructions that causes an external device to change tasks as a resultof transitioning from a first state to a second state. For example, thedigital assistant may transmit instructions that causes an externaldevice (e.g., a computer or phone) to transition from a first state to asecond state when the external device changes a song, transitions fromperforming one task to another (e.g., playing music to providing theweather), or transitions from an inactive state to an active state, andvice versa.

As illustrated in FIG. 8C, when there are multiple external devices(e.g., table lamp 818, floor lamp 814) in the room (or accessible byelectronic device 800), electronic device 800 is able to differentiatebetween the multiple external devices and only transmits instructions tothe intended external device (e.g., table lamp 818, floor lamp 814).Electronic device 800 identifies the intended external device (e.g.,table lamp 818, floor lamp 814) by determining whether the set of one ormore gaze criteria is met for a particular external device (e.g., tablelamp 818, floor lamp 814). In other words, electronic device 800 usesthe gaze information to determine which external device (e.g., tablelamp 818, floor lamp 814) the user is looking at, when the set of one ormore gaze criteria is satisfied. In some embodiments, when electronicdevice 800 transmits the instructions (e.g. “turn on”) to the identifiedfirst external device, table lamp 818, a second external device, floorlamp 814 in the room remains unaffected because floor lamp 814 is notthe external device identified by the gaze information. Floor lamp 814(the second external device) may be in an on state or an off state. Forexample, in FIG. 8C, the instructions are transmitted to table lamp 818causing table lamp 818 to turn on, but the instructions are nottransmitted to floor lamp 814, which remains off (floor lamp 814 waspreviously in the off state). Thus the transmitted instruction does notcause floor lamp 814 to change state. In some embodiments, when user 820glances at floor lamp 814 instead of table lamp 818, the set of one ormore gaze criteria is met by floor lamp 814, instead of table lamp 818.Accordingly, the digital assistant transmits the instructions to floorlamp 814, while table lamp 818 remains unaffected (e.g., table lamp 818remains on if it was previously on, and remains off if it was previouslyoff).

When the digital assistant has transmitted the instructions to thecorresponding external device, electronic device 800 optionally providesan indicator (e.g., indicator 810A, 810B, 810C) indicating that thetable lamp 818, has transitioned from a first state to a second state.In some embodiments, the indicator is a visual indicator 810A thatdisplays a light of a particular color (e.g., blue or a color other thanthe default color) or a light pattern to indicate that table lamp 818has turned on, from the off state, as a result of receiving theinstructions. In some embodiments, the indicator is an audio indicator810B that is a sound, one or more words, or a tone. In some embodiments,the indicator is an audio confirmation 810C from the digital assistant,such as “Ok, Jack, the table lamp is on.” The user may customize theindicators to include characteristics (e.g., a user name, particularuser preferences for light color, pattern, sound, voice, accent)associated with the user's profile, which user 820 provided duringregistration. The registration process is described in detail below withrespect to FIGS. 10A-10D and method 1100. The digital assistantcustomizes the indicator to reflect which user (e.g., Jack) wasrecognized, as discussed below with respect to FIGS. 10A-10D and method1100. In some embodiments, electronic device 800 provides the indicator(e.g., 810A, 810B, 810C) when the digital assistant has successfullysent instructions to table lamp 818, regardless of whether table lamp818 actually turned on. In some embodiments, electronic device 800provides the indicator (e.g., 810A, 810B, 810C) in response to adetermination that table lamp 818 has turned on. Optionally, electronicdevice 800 provides a different indicator (e.g., 810A, 810B, 810C) whentable lamp 818 was unable to execute the command to “turn on” andremains off. In some embodiments, the electronic device 800 may providea different indicator (e.g., 810A, 810B, 810C) to indicate a particularerror code when the command 824A-824B was unsuccessfully executed.

The indicators (e.g., 810A, 810B, 810C) are optionally domain (e.g.,music) specific. In some embodiments, the electronic device 800determines that the command refers to an action in a particular domain(e.g., “Love that song” command in the music domain). In accordance witha determination that the command is of a first domain (e.g., music), theindication is a first type of indication (e.g., a particular set ofsounds or light indictors). In accordance with a determination that thecommand is of a second domain (e.g., e-mail) different from the firstdomain, the indication is a second type of indication (e.g., a differentset of sounds or light indicators) different from the first type ofindication. Having different indicators (e.g., 810A, 810B, 810C) fordifferent domains allows the user to easily recognize when a command wasexecuted successfully versus when a command failed to execute.

FIG. 8D illustrates that once the digital assistant has transmitted theinstruction to turn on table lamp 818, user 820 may further change asetting of the external device (e.g., the brightness of the lamp) byproviding an input at a second external device (e.g., by rotating thecrown 832 of a watch 830 that user 820 is wearing). Watch 830 does nothave access to contextual information about which external device tocontrol. Instead, the user merely uses the crown 832 of watch 830 as anextended input mechanism to control the lamp. Watch 830 detects the userinput and sends an indication of the user input to electronic device800. Electronic device 800 receives the indication of the user input anddetermines that table lamp 818 is the intended external device (e.g.,table lamp 818, floor lamp 814) that should receive the instructions. InFIG. 8D, user 820 turns the crown 842 to increase the brightness of thetable lamp 818 to a brightness of 80. In some examples, electronicdevice 800 determines that table lamp 818 is the intended externaldevice based on the recency of electronic device 800 having transmittedinstructions to table lamp 818 based on user 820's actions. In someembodiments, the electronic device 800 transmits the instructions (basedon the user input at watch 830) to the most recent device (e.g., tablelamp 818) that the electronic device 800 instructed. For example, if theelectronic device 800 had just instructed the computer to play music,then the user turning the crown 842 on the watch 840, results inelectronic device 800 transmitting instructions to the computer toincrease (or decrease) the volume of the computer. In some embodiments,electronic device 800 is paired to table lamp 818. In some embodiments,the electronic device 800 detects that user 820 is wearing watch 840while watch 840 is paired with the electronic device 800. In someembodiments, watch 840 is (also) paired with the table lamp 818. Onceelectronic device 800 has sent instructions to table lamp 818,electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) toindicate that the instructions were successfully sent. In someembodiments, electronic device 800 provides a different indicator (e.g.,810A, 810B, 810C) indicating that the instructions were not successfullysent to table lamp 818.

FIG. 8E illustrates the electronic device 800 receiving an additionalindication of user input from watch 830 to dim the light of table lamp818 to a lower brightness, which corresponds to an amount of rotation ofcrown 832 by user 820. In response to receiving the indication of theinput from watch 830, electronic device 800 transmits an instruction totable lamp 818 to dim the lights from a brightness of 80 to a reducedbrightness of 20, based on the recency of having instructed table lamp818 to turn on. In some embodiments, user 820 uses watch 830 to directlycontrol table lamp 818 once table lamp 818 has been turned on withouthaving to provide additional commands to the digital assistant. Onceelectronic device 800 has sent instructions to table lamp 818,electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) toindicate that the instructions were successfully sent. In someembodiments, electronic device 800 provides a different indicator (e.g.,810A, 810B, 810C) indicating that the instructions were not successfullysent to table lamp 818.

In some embodiments, as illustrated in FIGS. 8F-8H, when there aremultiple external devices (e.g., floor lamp 814, table lamp 818) in theroom, electronic device 800 uses the user's gaze information to identifya particular external device as the intended external device based onthe user's gaze. Electronic device 800 identifies the intended externaldevice by determining whether the set of one or more gaze criteria ismet for the particular external device based on the gaze information.When the set of one or more gaze criteria is not satisfied for anyexternal device, electronic device 800 forgoes transmitting theinstruction because electronic device 800 is unable to determine theexternal device from the gaze information. As a result, the externaldevices in the room remain in their original states.

FIG. 8F illustrates electronic device 800 detecting gaze information ofuser 820 and, in accordance with a determination that the set of one ormore activation criteria has been satisfied (e.g., as discussed abovewith respect to FIGS. 6A-6D), the electronic device activates thedigital assistant. The electronic device may optionally provide a visualindicator 810A (e.g., turning on display 802), audio indicator 810B, ora digital voice confirmation 810C to indicate that the digital assistantis activated.

FIG. 8G illustrates a table lamp 818 that is initially on and floor lamp814 that is initially off. Electronic device 800 detects user 820speaking a second command 824C to “turn on that light.” However, user820 does not look at floor lamp 814, which is the intended externaldevice of command 826C. Electronic device 800 obtains second gazeinformation through the one or more camera sensors 816A that may belocated on external devices and/or is integrated with electronic device800 at camera 816B. The second gaze information optionally includes oneor more of: the position of the user's head position, the dwell time orduration of the gaze, the direction of the gaze, the field of view 806of the gaze, the direction of the gaze, and whether floor lamp 814 iswithin the field of view 806 of the gaze.

In FIG. 8H, electronic device 800 determines that the second gazeinformation obtained from the one or more camera sensors 816 does notmeet the set of one or more gaze criteria. As discussed above, the setof one or more gaze criteria optionally includes a direction criterionthat is satisfied for floor lamp 814 when the gaze is directed in thedirection of floor lamp 814. The set of one or more gaze criteriaoptionally includes a dwell time criterion that is satisfied for floorlamp 814 when electronic device 800 detects a dwell time or duration ofthe gaze in the direction of floor lamp 814 for greater than apredetermined period of time (e.g., a non-zero threshold, two seconds).The set of one or more gaze criteria optionally includes a field of viewcriterion. The field of view criterion is satisfied for floor lamp 814when floor lamp 814 is determined to be in field of view 808 of user820. FIGS. 8G-8H illustrates that floor lamp 814 and table lamp 818 arenot determined to be in field of view 808 of user 820 because thedetermined offset angles is greater than the threshold offset angle fromuser 820's line-of-sight 812. The threshold offset angle 804 is greaterthan zero degrees (e.g., thirty degrees). When the set of one or moregaze criteria is not met because one or more of a duration criterion,dwell time criterion, and/or field of view criterion are not met for anyexternal device, electronic device 800 is unable to determine whichexternal device (floor lamp 814, table lamp 818) user 820 intends to acton (e.g., to turned on).

FIG. 8H illustrates that because the set of one or more gaze criteriawas not met for any external device, electronic device 800 forgoestransmitting the instruction “turn on that light” to transition theexternal device, floor lamp 814 or table lamp 818, from the first state(e.g., off) to the second state (e.g., on). As a result, floor lamp 814remains off and table lamp 818 remains off, which was the initial statesof the external devices prior to electronic device 800 detecting user820 speaking the command 824C. For example, table lamp 818 remains inits on state because no instructions have been sent to table lamp 818 tochange its initially on state.

Electronic device 800 optionally produces a particular indicator (e.g.,810A, 810B, 810C) (e.g., a sequence of lights such as a headshakeindication (e.g., FIG. 6O or sounds) to indicate that electronic device800 did not transmit the instructions because it could not identify thefloor lamp 814 (or any other device) as the intended external devicebased on the gaze information of user 820. In some embodiments, aparticular indicator (e.g., pattern of light, color, or particularsound) may correspond to a particular error code for why the digitalassistant was unable to determine the external device associated withcommand 824C. The indicator produced when the digital assistant isunable to transmit the instructions is optionally different than theindicator produced when the digital assistant is able to transmit theinstruction. In some embodiments, no indicator is produced when thedigital assistant does not transmit the instructions associated withcommand 824C.

FIG. 8I illustrates another embodiment where there are multiple externaldevices (e.g., floor lamp 814 and table lamp 818) in the room and pairedto electronic device 800. In this example, the digital assistant hasbeen activated by user 820's glance. In other examples, the digitalassistant is activated by a word, a glance, or by a button press, asdiscussed above. As shown in FIG. 8I, prior to the user speaking command824A-824B in FIGS. 8J-8L, table lamp 818 is already in an on state,while floor lamp 814 is in an off state.

In FIG. 8J, electronic device 800 detects user 820 speak a portion 824A,“Turn . . . ”, of a second command 824A-824B to “turn on that light”while detecting that user 820 is looking at floor lamp 814. At FIG. 8J,electronic device 800 obtains second gaze information based on theuser's glance at floor lamp 814 through the one or more camera sensors816A that may be located on external devices and/or is integrated withelectronic device 800 at camera 816B. The second gaze informationoptionally includes one or more of: the position of the user's headposition, the dwell time or duration of the gaze, the direction of thegaze, the field of view of the gaze, the direction of the gaze, andwhether floor lamp 814 is within the field of view of the gaze based onan offset angle.

Electronic device 800 determines whether the second gaze informationobtained from the one or more camera sensors 816A-816B satisfies a setof one or more gaze criteria. When the set of one or more gaze criteriais met for floor lamp 814, electronic device 800 is able to determinethat user 820 intended the second command 824A-824B to be applied tofloor lamp 814. As discussed above, the set of one or more gaze criteriaoptionally includes a direction criterion that is satisfied for floorlamp 814 when the gaze is directed in the direction of floor lamp 814.The set of one or more gaze criteria optionally includes a dwell timecriterion that is satisfied when electronic device 800 detects a dwelltime or duration of the gaze in the direction of floor lamp 814 forgreater than a non-zero, predetermined period of time (e.g., twoseconds). The set of one or more gaze criteria optionally includes afield of view criteria. The field of view criterion is satisfied whenexternal device, floor lamp 814, is determined to be in field of view808 of user 820. Floor lamp 814 is determined to be in field of view 808of user 820 when floor lamp 814 is within a threshold offset angle 804from a user's line of-sight 812. In some embodiments, the field of viewcriterion is satisfied when floor lamp 814 is directly in theline-of-sight 812 of user 820, as shown in FIG. 8J. In some embodiments,a field of view criterion is satisfied when a determined offset angle ofthe gaze is less than the threshold offset angle (e.g., the maximumacceptable deviation from a line-of-sight 812 of user 820 lookingdirectly at floor lamp 814). The threshold offset angle 804 isoptionally greater than zero degrees (e.g., thirty degrees). Thedetermined offset angle is calculated based on the angle formed betweena line-of-sight 812 from a gaze of user 820 and a calculatedline-of-sight 808 from user 820 to electronic device 800. In someexamples, when floor lamp 814 is in the field of view of the gaze bybeing within the threshold number of degrees from the user's directline-of-sight 812, the field of view criterion is met for floor lamp814.

In some embodiments, as shown in FIG. 8K, user 820 breaks his gaze atthe floor lamp 814 while speaking the remaining portion 824B of thesecond command 824A-824B. FIG. 8K illustrates electronic device 800detecting that user 820 is looking away from floor lamp 814, therebybreaking his gaze with floor lamp 814 while speaking the second portion824B of second command 824A-824B. In some embodiments, when electronicdevice 800 has already determined that floor lamp 814 is the intendedexternal device prior to user 820 looking away, the set of one or moregaze criteria is still met even though user 820 has broken his/her gazeprior to completing second command 824A-824B. In some embodiments, ifelectronic device 800 detects that user 820 returns his gaze back tofloor lamp 814 within a threshold duration, prior to completing command824A-824B (e.g., FIGS. 6E-6G) electronic device 800 still identifies thefloor lamp 814 as the external device.

When the set of one or more gaze criteria is met, the electronic devicetransmits the instruction to floor lamp 814, causing floor lamp 814 totransition from an off state to an on state, as shown in FIG. 8L. Tablelamp 818 remains in the prior on state, because table lamp 818 does notmeet the set of one or more gaze criteria, and therefore, the electronicdevice does not transmit instructions for changing the state of thetable lamp 818. In some embodiments, if the command 824C received byelectronic device 800 was determined to be directed to floor lamp 814and included “turn off that light,” when the set of one or more gazecriteria is met for floor lamp 814, electronic device 800 would transmitinstructions to turn off floor lamp 814, while table lamp 818 that waspreviously in the on state would remain on.

FIG. 8L illustrates when electronic device 800 has transmitted theinstruction to floor lamp 814, electronic device 800 optionally providesan indicator (e.g., indicator 810A, 810B, 810C) indicating that floorlamp 814 has transitioned from an off state to an on state. In someembodiments, the indicator is a visual indicator 810A that displays alight of a particular color (e.g., blue or a color other than thedefault color) or a light pattern to indicate that table lamp 818 hasturned on, from the off state, as a result of receiving theinstructions. In some embodiments, the indicator is an audio indicator810B that plays a sound, one or more words, or a tone. In someembodiments, the digital assistant speaks a confirmation 810C. In someembodiments, user 820 may customize the audio and visual indicators toinclude characteristics (e.g., a user name, particular user preferencesfor light color, pattern, sound, voice, accent) associated with his/heruser profile. In FIG. 8K, the digital assistant provides an audioindicator, “Jack, floor lamp turned on.” The audio indicator provides aconfirmation that the instruction was executed. The audio indicator alsoincludes the name of user 820, which was obtained from the user profileof user 820, which user 820 provided during registration. Theregistration process is described in detail below with respect to FIGS.10A-10D. The digital assistant may utilize settings from user 820'sprofile to further customize the indicator to reflect which user (e.g.,Jack) has spoken the command. In some embodiments, electronic device 800provides the indicator when the electronic device has successfully sentinstructions to “turn on” to floor lamp 814, regardless of whether floorlamp 814 actually turned on. Optionally, electronic device 800 providesa different indicator when floor lamp 814 was unable to execute thecommand to “turn on” and remains off. In some embodiments, the indictorwhen the command 824C was unsuccessfully executed includes differentindicators for different error codes.

FIGS. 9A-9B are flow diagrams illustrating a method for 900 using anelectronic device in accordance with some embodiments. Method 900 isperformed at an electronic device (e.g., 100, 300, 500, 600, 640, 800,1000). Some operations in method 900 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 900 provides an intuitive way for the user(e.g., 820) to provide context for an audio user input request to adigital assistant on an electronic device (e.g., 800) by glancing at theexternal device (e.g., 814, 818) that the audio user input request isintended to operate on. The method reduces the cognitive burden on auser (e.g., 820) when providing audio user input request (e.g., havingto remember to say the external device in the command) to the digitalassistant. Therefore, the digital assistant is able to determine theexternal device (e.g., 814, 818) for the command by monitoring the gazeof the user (e.g., 820).

While a first external device (e.g., 818) is in a first state (902)(e.g., the first external device (e.g., 818) is on or off, the firstexternal device (e.g., 818) is playing a particular media item) theelectronic device (e.g., 800) receives (904) an audio user input request(e.g., a user speech input) to perform a first command (e.g., 824A-824B)(e.g., to transition the external device to a second state, telling thedigital assistant to “turn on that light”). In some embodiments, theelectronic device receive (904) the audio user input request while thedigital assistant on the electronic device (e.g., 800) is active (e.g.,based on a trigger word, gaze, and/or button press).

While the first external device (e.g., 818) is in the first state (902),the electronic device obtains (906), using one or more camera sensors(e.g., 816A, 816B) (e.g., infrared camera sensor(s), visible lightsensor(s)); from camera(s) external to the electronic device (e.g., 800)such as wirelessly connected to the electronic device or part of theelectronic device (e.g., 800)), first gaze information (e.g., theelectronic device (e.g., 800) detects gaze information that is directedat the first external device (e.g., 818)). In some examples, theelectronic device (e.g., 800) determines, using the first gazeinformation, whether a set of one or more gaze criteria is met for aparticular external device.

In accordance with a determination (908) (and, optionally, in responseto the electronic device (e.g., 800) receiving the audio user inputrequest), using the first gaze information, that a set of one or moregaze criteria is met for the first external device (e.g., 818) (e.g.,appliance such as a lamp, tv, or computer): the electronic device (e.g.,800) transmits (910) (e.g., to the first external device (e.g., 818)),based on the first command, an instruction to transition the firstexternal device (e.g., 818) from the first state to a second state(e.g., the digital assistant performs an action on the external device(e.g., 818) by causing the external device (e.g., 818) to transitionfrom an ON state to an OFF state or from an OFF state to an ON state).

Using gaze detection to determine which external device (e.g., 814, 818)is associated with the command (e.g., 824A-824B) when the set of one ormore gaze criteria is satisfied provides the user with a more efficientuser interface for providing context to the digital assistant simply bylooking at the external device (e.g., 814, 818) without having to answerfollow up questions from the digital assistant to clarify which externaldevice (e.g., 814, 818) is intended. Providing improved user interfacesto provide context to a command (e.g., 824A-824B) to the digitalassistant without the digital assistant having to interact with the userto obtain more information makes the user interface of the digitalassistant interface more efficient. In addition, using gaze detectionreduces the number of inputs needed to activate the digital assistant toperform commands (e.g., 824A-824B), which enhances the operability ofthe digital assistant.

In some embodiments, in accordance with the determination that the setof one or more gaze criteria is met for the first external device (e.g.,818) (e.g., angle, duration, and direction of gaze), the electronicdevice (e.g., 800) provides (912) an indication (e.g., 810A, 810B, 810c) (e.g., visual or audio indication) that the set of one or more gazecriteria is met (e.g., indicating that the first command (e.g.,824A-824B) is associated with the first external device (e.g., 818)).

Providing an indication that the set of one or more gaze criteria hasbeen satisfied and that the digital assistant has successfullytransmitted the instructions to the external device (e.g., 800) providesthe user with feedback about whether the command (e.g., 824A-824B) wasexecuted. The indication (e.g., 810A, 810B, 810C) can be visual, audio,or a digital assistant voice confirmation, which provides customizablefeedback for various contexts. For example, in contexts where soundcannot be heard (e.g., a noisy room), providing visual feedback allowsthe user to know whether the digital assistant has transmitted thecommand (e.g., 824C). Providing customized feedback of the state of thedigital device enhances the operability of the digital assistant andmakes the user-device interface more efficient (e.g., the user doesn'thave to repeat the command because the user is not sure if it wascarried out by the digital assistant) by informing the user when thedigital assistant has successfully transmitted the command to theexternal device. Further, the feedback of the state of the digitalassistant allows the user to use the device more quickly andefficiently.

In some embodiments, the indication (e.g., 810A, 810B, 810C) (e.g.,visual or audio indication) is domain specific (914) (e.g., musicdomain, weather domain, messaging domain). In some examples, theelectronic device (e.g., 800) determines that the command (e.g., 824C)is of a particular domain. In accordance with a determination that thecommand (e.g., 824C) is of a first domain, the indication (e.g., 810A,810B, 810C) is a first type of indication. In accordance with adetermination that the command (e.g., 824C) is of a second domaindifferent from the first domain, the indication (e.g., 810A, 810B, 810C)is a second type of indication different from the first type ofindication.

Providing domain specific indications quickly informs the user (e.g.,820) whether the digital assistant was able to transmit the instructionsfor the command (e.g., 824C) successfully. Associating particularvisual, audio, or digital voice indicators with particular domainsprovide the user quickly with an improved user interface that allows theuser quickly to quickly determine whether more action needs to be takenif the command (e.g., 824C) was not successfully carried out. Forexample, when the user quickly says “love that song” a particular tonethat is played and associated with the command informs the user (e.g.,820) quickly that the digital assistant has added the song to afavorites list, without the user quickly having to verify it was added.This reduces the cognitive burden on the user quickly as the associationof the success tone with a particular action in a particular domainprovides immediate confirmation that the task was carried out. Further,the feedback of the state of the digital assistant allows the user(e.g., 820) to use the digital assistant more quickly and efficiently.

In some embodiments, the electronic device (e.g., 800) is paired (916)to the first external device (e.g., 814, 818) (e.g., a paired lamp, tv,computer, phone or watch).

In some embodiments, in accordance with a determination, using the firstgaze information, that the set of one or more gaze criteria is not met(e.g., user breaks gaze; user is not looking at an external device for athreshold period of time) for the first external device (e.g., 814,818), the electronic device (e.g., 800) forgoes transmitting theinstruction to transition the first external device (e.g., 818) from thefirst state to the second state. In some examples, the digital assistantdoes not perform the command (e.g., 824C), when the set of one or moregaze criteria is not met.

In some embodiments, the set of one or more gaze criteria includes afield of view criterion that is met when a determined offset angle(e.g., 810) is less than a threshold offset angle (e.g., 804) (e.g., themaximum acceptable deviation from the user looking directly at thedevice; a non-zero threshold offset angle; the threshold offset angle isgreater than zero degrees), wherein the determined offset angle (e.g.,810) is an angle formed between: a line-of-sight (e.g., 812) (e.g.,determined from the gaze information) of a gaze of a user, and acalculated line-of-sight (e.g., 808) from the user (e.g., 820) to thefirst external device (e.g., 818). In some examples, if the firstexternal device (e.g., 818) is determined to be positioned more than athreshold number of degrees (e.g., outside the field of view (e.g., 806)of the gaze), the first external device (e.g., 818) is not in the user'sgaze and the instruction is not sent to the first external device (e.g.,818). In some examples, when the first external device (e.g., 818) is inthe field of view (e.g., 806) of the gaze by being within the thresholdnumber of degrees, the digital assistant sends the instruction to thefirst external device (e.g., 818).

Using a field of view criterion as a gaze criteria allows the user'sgaze to be detected without requiring the user to look directly at theexternal device (e.g., 818). Instead, as long as the external device(e.g., 818) is within a field of view of the user's gaze, the user'sgaze satisfies the gaze criteria, allowing the electronic device (e.g.,800) to determine which external device (e.g., 814, 818) is intended.Using the field of view criterion allows the external device (e.g., 818)to be determined without requiring further interaction with the user,which enhances the operability of the digital assistant and makes thegaze detection by the electronic device (e.g., 800) more efficient(e.g., the external device (e.g., 818) is more easily identified sincethe external device (e.g., 818) does not have to be in the directline-of-sight of the user (e.g., 820)).

In some embodiments, the line-of-sight (e.g., 812) of the gaze of theuser (e.g., 820) is based on a head position of the user (e.g., 820)(e.g., the same user from whom the audio user input request wasreceived). In some examples, the user's head position may be affected bythe tilt or rotation (e.g., yaw, pitch, and roll) of the user's head. Insome examples, head position tracking is used to determine whether thefirst external device (e.g., 818) is in the field of view (e.g., 806).

In some embodiments, the set of one or more gaze criteria includes adwell time criterion that is met for the first external device (e.g.,818) when a dwell time (e.g., duration) of the gaze determined from thefirst gaze information is more than a threshold period of time (e.g., anon-zero period of time). In some examples, when the dwell time of thegaze of the user (e.g., 820) is less than a threshold amount of time.

In some embodiments, subsequent to the electronic device (e.g., 8000)transmitting (e.g., to the first external device (e.g., 818)) theinstruction to transition the first external device (e.g., 818) from thefirst state to the second state, the electronic device (e.g., 800)provides an indication (e.g., 810A, 810B, 810C) (e.g., audio or visual)that the first external device (e.g., 818) is in the second state (e.g.,the electronic device (e.g., 800) provides a visual indication (e.g.,810A) to indicate that the first external device (e.g., 818) has turnedon). In some examples, the electronic device (e.g., 800) provides adifferent indication (e.g., 810A, 810B, 810C) when the command (e.g.,824C) was not able to be executed (e.g., the first external device(e.g., 818) is still in the first state).

In some embodiments, while the first external device (e.g., 818) is inthe first state and a second external device is in a third state and inaccordance with a determination (and, optionally, in response toreceiving the audio user input request), using the first gazeinformation, that the set of one or more gaze criteria is met for thesecond external device (e.g., appliance such as a lamp, tv, orcomputer): the electronic device (e.g., 800) transmits (e.g., to thefirst external device (e.g., 818)), based on the first command (e.g.,824C), an instruction to transition the second external device (e.g.,814) from the third state to a fourth state (e.g., the electronic device(e.g., 800) performs an action on the second external device (e.g., 814)by transitioning the second external device from an ON state to an OFFstate or from an OFF state to an ON state).

In accordance with a determination (and, optionally, in response toreceiving the audio user input request), using the first gazeinformation, that the set of one or more gaze criteria is not met forthe second external device (e.g., 814) (e.g., appliance such as a lamp,tv, or computer): the electronic device (e.g., 800) forgoes transmitting(e.g., to the first external device), based on the first command (e.g.,824C), the instruction to transition the second external device (e.g.,814) from the third state to the fourth state (e.g., the electronicdevice (e.g., 800) forgoes performing an action on the second externaldevice, such as forgoing transitioning the second external device froman ON state to an OFF state or from an OFF state to an ON state).

In some embodiments, while the first external device (e.g., 818) is inthe second state (e.g., the first external device 9 e.g., 818) may alsobe in the first state) and a second external device (e.g., 814) is in athird state (918): the electronic device (e.g., 800) receives (920) asecond user input request (e.g., a user speech input) including a secondcommand (e.g., 826C).

The electronic device (e.g., 800) obtains (922), using one or morecamera sensors (e.g., 816A, 816B), second gaze information (e.g., totransition the second external device (e.g., 814) to a second state,telling the digital assistant to turn on “that” light).

In accordance with a determination, using the second gaze information,that the set of one or more gaze criteria is met for the second externaldevice (e.g., 814) (e.g., the second gaze identifies a second externaldevice (e.g., 814) by satisfying gaze criteria such as the angle of thegaze being within a threshold number of degrees, gaze is in a particulardirection, duration is greater than or equal to a predetermined timeperiod.): the electronic device (e.g., 800) transmits (924), based onthe second command (e.g., 824C), an instruction to transition the secondexternal device (e.g., 814) from the third state to a fourth state(e.g., changing the state of the second external device (e.g. 814): thefloor lamp turned on) while the first external device (e.g., 818)remains in the second state (e.g., without changing the state of thefirst external device: the table lamp remains on).

In some embodiments, while the second external device (e.g., 814) is inthe third state and in accordance with a determination, using the secondgaze information, that the set of one or more gaze criteria is not metfor the second external device (e.g., 814) (e.g., second external deviceis not identified): the electronic device (e.g., 800) forgoes (926)transmitting the instruction to transition the second external device(e.g., 814) from the third state to the fourth state (e.g., secondexternal device (e.g., 814) remains in the same state as before).

In some embodiments, subsequent to transmitting (e.g., to the secondexternal device (e.g., 814) the instruction to transition the secondexternal device (e.g., 814) from the third state to the fourth state,the electronic device (e.g., 800) provides an indication (e.g., 810A,810B, 810C) (e.g., visual or audio indication) that indicates that thesecond external device (e.g., 814) is in the fourth state (e.g., providea visual (e.g., 810A) or audio (e.g., 810B) indication to indicate thesecond external device (e.g., 814) has changed state). In some examples,the electronic device (e.g., 800) provides a different indication (e.g.,810A, 810B, 810C) when the second command (e.g., 824C) was not able tobe executed, (e.g., the second external device (e.g., 813) is still inthe third state).

In some embodiments, subsequent to transmitting (e.g., to the firstexternal device (e.g., 818)) the instruction to transition the firstexternal device (e.g., 818) from the first state to the second state:the electronic device (e.g., 800) receives from the third externaldevice (e.g. a watch or a phone), an indication of an input received bythe third external device (e.g., 830) (e.g., rotation of a crown (e.g.,832) on a third external device). The electronic device (e.g., 800)transmits a second instruction, to the first external device (e.g., 818)based on a recency of the electronic device (e.g., 800) havinginstructed the first external device (e.g. 818) (e.g., a thirdinstruction to transition the first external device (e.g., 818) (e.g.,dim the brightness of the light of the table lamp after the table lamphas been turned on). In some examples, third external device (e.g., 830)doesn't know which external device (e.g., 814, 818) the third externaldevice (e.g., 840) is interacting with. The third external device (e.g.,830) only receives the input and transmits the user input to theelectronic device (e.g., 800), which is the device that figures outwhich external device (e.g., 814, 818) to send the instruction to (e.g.,dim the light).

Using a third external device (e.g., 830) to further control the mostrecent external device (e.g., 818) that the electronic device (e.g.,800) sent an instruction to, provides the user (e.g., 820) withadditional user interfaces to have more control over the external device(e.g., 818).

Providing a user (e.g., 820) with additional user interfaces andmechanisms for control devices without having to go through the digitalassistant provides more efficient user interfaces and reduces the numberof interactions needed with the digital assistant to perform a command.Rather than having to interact with the digital assistant to processadditional commands, the user (e.g., 820) may simply use an externaldevice (e.g., 830) to provide more precise input that is sometimesdifficult to explain in words. Receiving additional user input based oninput received from a third external device (e.g., 840), enhances theoperability of the digital assistant and makes the user interface ofcontrolling external devices (e.g., 818) more efficient as additionalcommands are not needed.

Note that details of the processes described above with respect tomethod 900 (e.g., FIGS. 9A-9B are also applicable in an analogous mannerto the methods described below/above. For example, method 900 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 700 and below with reference tomethod 1100. For example, method 900 may include one or more of thecharacteristics of the various methods described above and below withreference to the processes in FIGS. 7A, 7B, 11A, and 11B. For brevity,these details are not repeated below.

It should be understood that the particular order in which theoperations in the following FIGS. 7A-7B and 11A-11B have been describedis exemplary and not intended to indicate that the described order isthe only order in which the operations could be performed. One ofordinary skill in the art would recognize various ways to reorder theoperations described herein, as well as excluding certain operations.For brevity, these details are not repeated here. Additionally, itshould be noted that aspects of the methods and processes describedthroughout this description may be incorporated with one another.

FIGS. 10A-10D illustrate exemplary user interfaces for providingdifferent indicators to indicate the digital assistant's recognition ofvarious users (e.g., 1020, 1030) speaking commands in a room, once thedigital assistant has been activated, in accordance with someembodiments. The digital assistant is activated based on a trigger word,a gaze as discussed above with respect to method 700, a button press, awrist raise while the user is wearing a wearable electronic device(e.g., a watch) (e.g., FIGS. 6E-6G), and/or the user pointing anexternal device (e.g., a phone) at electronic device 1000. In someexamples, the electronic device 1000 activates the digital assistant inresponse to determining that a user (e.g., 1020, 1030) is looking atelectronic device 1000 (e.g., in accordance with a determination that aset of one or more activation criteria are met using gaze information,as discussed above) and receives commands once the digital assistant isactivated. The techniques illustrated in FIGS. 10A-10D also optionallyinclude aspects of method 900 and the techniques described with respectto FIGS. 8A-8L, which illustrate an electronic device using the user'sgaze to determine a particular external object (e.g., table lamp 1018,floor lamp) associated with the command. The techniques in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 11A-11B.

As illustrated in FIGS. 10A-10D, users Jane 1030 and Jack 1020 are inthe same room as electronic device 1000. In FIG. 10A, the digitalassistant of electronic device is activated, such as using aspects ofthe techniques described above. Electronic device 1000 receives a spokencommand (e.g., 1024A, 1024B) from one or more users, (e.g., Jane 1030and Jack 1020), to control various external devices, such a floor lamp1014 or a table lamp 1018 in the room. In response to electronic device1000 receiving the command (e.g., 1024A, 1024B), electronic device 1000determines a user identity (e.g., 1020, 1030) of the particular user whospoke the command (e.g., 1024A, 1024B). In some embodiments, an externaldevice (e.g., external cameras 1016A, a phone, or integrated camera1016B) determines the user identity corresponding to the command, andsends the user identity to electronic device 1000. In some embodiments,electronic device 1000 obtains information about the user speaking usingan external or internal device (e.g., external cameras 1016A, a phone,or integrated camera 1016B). In some embodiments, the electronic device1000 uses the obtained information to perform facial recognition, voicerecognition, or to calculate a distance to the user speaking todetermine a user identity.

In some embodiments, prior to the electronic device activating thedigital assistant, users Jane 1030 and Jack 1020 have optionallyregistered user profiles that are stored on electronic device 1000. Insome embodiments, the user profiles are stored on a server and areaccessible by electronic device 1000. The user profiles include settingsand preferences (e.g., type of accent for the digital assistant voice,the gender for the digital assistant voice, indicator tones, LED lightcolors) that the electronic device may use to customize indicators1010A, 1010B, 1010C used by the electronic device to indicate when thedigital assistant is activated or when a command 1024A, 1024B has beensuccessfully or unsuccessfully performed. For example, the user maycustomize the digital indicator settings by providing a value for eachcharacteristic of the indicator. In some examples, the characteristicsof the indicator include the type (e.g., visual, audio, voiceconfirmation or a combination of any of the types), a light color for avisual indicator, a tone for an audio indicator, and customizations(e.g., language, type of accent and gender) for the digital voice. Theuser profile also optionally stores information about the user providedby users Jane 1030 and Jack 1020 during registration with the user'sconsent, such as the user's name, birthdate, gender, and/or address. Theuser profile settings and preferences may be updated at any time. Thetechniques for user registration on electronic device 1000 describedhere may be used above in combination with methods 700 and 900 withreference to the processes in FIGS. 7A, 7B, 9A, and 9B. For brevity,these details are not repeated above.

In FIG. 10A, electronic device 1000 receives command 1024A, “turn on thetable lamp,” from Jane 1030 when the digital assistant is activated. Aselectronic device 100 is receiving the command 1024A being spoken byJane 1030 (or after receiving the command 1024A spoken by Jane 1030),electronic device 1000 determines that the speaker is Jane 1030. Forexample, device 1000 uses the external cameras 1016A, integrated camera1016B, and/or microphones, determines that the received command 1024A iscoming from the direction in which Jane 1030 is sitting. Accordingly,electronic device 1000 displays a light pattern 1010D (e.g., threeilluminated dots) on display 1002 in a position that corresponds to thedirection in which Jane 1030 is sitting. In some embodiments, electronicdevice 1000 displays an animated light pattern 1010D on display 1002,where the light pattern is animated to point to the direction in whichJane 1030 is sitting.

In FIG. 10A, when the digital assistant determines that the speaker ofcommand 1024A is Jane 1030, electronic device 1000 updates a value of acharacteristic (e.g., a color of a light, a particular sound, words, ora specific digital assistant voice) of an indicator (e.g., visual 1010A,audio 1010B, or a digital assistant confirmation 1010C) to a valuecorresponding to Jane 1030 (e.g., a purple light, a two-note tone,Jane's name, a British accent, female voice). In some embodiments, thevalue of the characteristic is a value obtained from Jane's userprofile. For example, the electronic device sets the color of lightpattern 1010D (e.g., three illuminated dots) on display 1002 to be acolor (such as purple) that corresponds to Jane 1030. As a result,electronic device 1000 indicates to Jane 1030 and Jack 1020 that device1000 has recognized the speaker as Jane 1030 and that one or more of thepreferences of Jane 1030 will be used.

In contrast, in FIG. 10C when the digital assistant determines that thespeaker of command 1024B is Jack 1020, who is a different user than Jane1030, electronic device 1000 updates the value of the characteristic(e.g., a color of a light, a sound, or a digital assistant voice) of theindicator (e.g., a visual indicator or an audio indicator) to a valuecorresponding to Jack 1020 (e.g., a blue light, a one-note tone, Jack'sname, an Australian accent, male voice), where the value of thecharacteristic associated with Jack 1020 is different form the value ofthe characteristic associated with Jane 1030. For example, theelectronic device sets the color of light pattern 1010E (e.g., threeilluminated dots) on display 1002 to be a color (such as blue) thatcorresponds to Jack 1020. As a result, electronic device 1000 indicatesto Jane 1030 and Jack 1020 that device 1000 has recognized the speakeras Jack 1020 and that one or more of the preferences of Jack 1020 willbe used.

In some embodiments, Jack 1020 and Jane 1030 may have values ofcharacteristics associated with each person that are the same. Forexample, Jack 1020 and Jane 1030 may both choose the American, female,digital assistant voice. In some embodiments, the values of thecharacteristic of the indicators associated with each user is unique.For example Jane 1030 and Jack 1020 may have different light colors(e.g., purple for Jane vs. blue for Jack) and different sounds (e.g.,two note sound vs. one note sound) associated with the respective user.

In FIG. 10B, once electronic device 1000 has identified that Jane 1030is speaking the command 1024A, electronic device 1000 determines whethera set of one or more performance criteria are met, as discussed abovewith respect to method 900. The set of one or more performance criteriaincludes one or more of: a completion criterion, an actionablecriterion, and an activation criteria. When the set of one or moreperformance criteria are met, electronic device 1000 performs theaction, such as transmitting the instructions to floor lamp 1014 to beturned on.

When electronic device 1000 has performed command 1024A, electronicdevice 1000 optionally provides an indicator (e.g., indicator 1010A,1010B, 1010C) using Jane's 1030 preferences to indicate that the commandhas been successfully performed. The types of indicators (e.g., visual,audio, and digital voice confirmations) and their characteristics arediscussed above with respect to method 700 and 900. In FIG. 10B,electronic device 1000 has determined that the speaker is Jane 1030 and,based on that determination, provides a confirmation using a femaledigital assistant voice confirmation with an American accent, “Jane, thefloor lamp has been turned on.” The name “Jane” is obtained from Jane's1030 user profile, which Jane 1030 provided during registration.Electronic device 1000 uses a female American accent based on a previouspreference stored as part of Jane's 1030 user profile. A purple lightpattern may be displayed as the visual indicator on electronic device1000 to indicate that the digital assistant has processed Jane's command1024A. A tone associated with Jane 1030 may also be played as the audioindicator on electronic device 1000 to indicate that the digitalassistant has processed Jane's command 1024A. As a result, both Jane1030 and Jack 1020 recognize that Jane was identified as the speaker.

FIG. 10C similarly illustrates Jack 1020 speaking command 1024B “turn onthe floor lamp.” Electronic device 1000 determines that the speaker isJack 1020 using, for example, external cameras 1016A, integrated camera1016B, and/or microphones to determine that the command 1024B is comingfrom the direction in which Jack 1030 is sitting. In response,electronic device 1000 displays a light pattern 1010E (e.g., threeilluminated dots) on display 1002 in a position that corresponds to thedirection in which Jack 1020 is standing. In some embodiments,electronic device 1000 displays an animated light pattern 1010E ondisplay 1002, where the light pattern is animated to point to thedirection in which Jack 1020 is standing. For example, the electronicdevice sets the color of light pattern 1010E (e.g., three illuminateddots) on display 1002 to be a color (such as blue) that corresponds toJack 1020. As a result, electronic device 1000 indicates to Jane 1030and Jack 1020 that device 1000 has recognized the speaker as Jack 1020and that one or more of the preferences of Jack 1020 will be used.

In FIG. 10D, once electronic device 1000 has identified that Jack 1020is speaking the command 1024B, electronic device 1000 determines whethera set of one or more performance criteria are met, as discussed abovewith respect to method 900. The set of one or more performance criteriaincludes one or more of: a completion criterion, an actionablecriterion, and an activation criteria. When the set of one or moreperformance criteria are met, electronic device 1000 performs theaction, such as transmitting the instructions to floor lamp 1014 to beturned on.

When electronic device 1000 has performed command 1024B, electronicdevice 1000 optionally provides an indicator (e.g., indicator 1010A,1010B, 1010C) using Jacks' 1020 preferences to indicate that the commandhas been successfully performed. The types of indicators (e.g., visual,audio, and digital voice confirmations) and their characteristics arediscussed above with respect to method 700 and 900. In FIG. 10D,electronic device 1000 has determined that the speaker is Jack 1020 and,based on that determination, provides a confirmation using a maledigital assistant voice with an Australian accent, “Jack, the table lamphas been turned on.” The name “Jack” is obtained from Jack's 1030 userprofile, which Jack 1020 provided during registration. Electronic device1000 uses a male Australian accent based on a previous preference storedas part of Jack's 1020 user profile. A blue light pattern may bedisplayed as the visual indicator on electronic device 1000 to indicatethat the digital assistant has processed Jack's command 1024B. Theelectronic device optionally plays a custom tone associated with Jack1020 as the audio indicator to indicate that the digital assistant hasprocessed Jack's command 1024B.

FIGS. 11A-11B are a flow diagrams illustrating a method 1100 using anelectronic device in accordance with some embodiments. Method 1100 isperformed at an electronic device (e.g., 100, 300, 500, 600, 640, 800,1000). Some operations in method 1100 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 1100 provides an intuitive way for thedigital assistant to show recognition of different users (e.g., 1020,1030) by providing unique indicator for each person. The method reducesthe cognitive burden on a user (e.g., 1020, 1030) because the user isable to confirm that the digital assistant processed the command of aparticular user when multiple users are speaking commands in the room.Therefore, the digital assistant is able to provide immediate feedbackto indicate which user's commands were processed.

After the digital assistant on the electronic device (e.g., 1000) hasbeen activated based on a trigger word, gaze, and/or button press,electronic device 1000 receives (1106) an audio user input request(e.g., 1024A, 1024B). In some examples, in response to receiving theaudio user input request (e.g., 1024A, 1024B), the electronic device(e.g., 1000) determines a user identity (e.g., a particular user (e.g.,1020, 1030)) corresponding to the audio user input request (e.g., 1024A,1024B). In some examples, a remote device (e.g., cameras 1016)determines the user identity corresponding to the audio user inputrequest (e.g., 1024A, 1024B) and the electronic device (e.g., 1000)receives results of the determination.

In some embodiments, prior to the electronic device (e.g., 1000)receiving the audio user input request (e.g., 1024A, 1024B), theelectronic device (e.g., 1000) receives (1102) registration information(e.g., user profile information). In some embodiments, the electronicdevice (e.g., 1000) associates (1104), using the registrationinformation, a first value of a characteristic (e.g., a light, a sound,a digital assistant voice) of an indicator (e.g., 1010A, 1010B, 1010C)of electronic device (e.g., 1000) with a first user (e.g., 1020) (andnot the second user) and a second value of the characteristic of anindicator of electronic device (e.g., 1000) with a second user (e.g.,1030) (and not the first user). In some examples, during a registrationprocess, the electronic device (e.g., 1000) receives a name of a userand later associates the name with the voice of the user (e.g., 1020,1030). In some examples, during a registration process, the electronicdevice (e.g., 1000) associates a color of a visual indicator (e.g., LEDcolor) to the user (e.g., 1020, 1030).

Associating values of a characteristic of the indicator (e.g., 1010A,1010B, 1010C) with preferences from the user's user profile, enables thedigital assistant to provide feedback to confirm the digital assistanthas identified the specific user (e.g., 1020, 1030) speaking thecommand. Providing customized feedback to confirm the user (e.g., 1020,1030) enhances the operability of the digital assistant and makes theuser-device interface more efficient (e.g., the user (e.g., 1020, 1030)knows the digital assistant has processed the user's command (e.g.,1024A, 1024B)) by providing confirmation to the user (e.g., 1020, 1030)using the user's preferences in the indicator (e.g., 1010A, 1010B,1010C). This reduces the cognitive burden on the user (e.g., 1020, 1030)as the association of the success indicator with a particular user'ssettings provides immediate confirmation that the task was carried outand reduces the confusion when there are multiple users speakingsimultaneously or other speakers in the background. Further, thefeedback of the state of the digital assistant allows the user (e.g.,1020, 1030) to use the digital assistant more quickly and efficiently.

The electronic device receives (1106) an audio user input request.

In some embodiments, the audio user input request (e.g., 1024A, 1024B)is a user speech input (e.g., utterance, a command) and the updating of(1108) the value of the characteristic (e.g., a light, a sound, adigital assistant voice) is not based on transcribed contents of theaudio user input request (e.g., 1024A, 1024B) (e.g., the value of thecharacteristic is not based on the words said by the user, but insteadis based on the identity of the user).

In accordance with a determination that the audio user input requestcorresponds to a first user (e.g., 1020) (and, optionally, in responseto receiving the audio user input request), the electronic device (e.g.,1000) updates (1110) a value of a characteristic (e.g., a color of alight, a sound, or a digital assistant voice) of an indicator (e.g.,1010A, 1010B, 1010C) (e.g., a visual indicator, an audio indicator, or adigital assistant voice confirmation) to a first value corresponding tothe first user (e.g., 1020) (e.g., the value of the characteristic isassociated with the identity of the first user).

In accordance with a determination that the audio user input requestcorresponds to a second user (e.g., 1030) (and, optionally, in responseto receiving the audio user input request), different from the firstuser, electronic device (1000) updates (1112) the value of thecharacteristic (e.g., a color of a light, a sound, or a digitalassistant voice) of the indicator (e.g., 1010A, 1010B, 1010C) (e.g., avisual indicator, an audio indicator, or a digital assistant voiceconfirmation) to a second value corresponding to the second user (e.g.,1030) (e.g., the value of the characteristic is associated with theidentity of the second user), the second value being different from thefirst value.

The electronic device (e.g., 1000) responds (1114) to the audio userinput request (e.g., 1024A, 1024B) using the indicator (e.g., 1010A,1010B, 1010C) (e.g., the electronic device (e.g., 1000) displays alight, plays a sound, using a particular digital assistant voice, orusing the user's name in the response), wherein the indicator (e.g.,1010A, 1010B, 1010C) includes the updated value of the characteristic(e.g., a color of a light, a sound, or a digital assistant voice).

In some embodiments, the electronic device (e.g., 1000) responding tothe audio user input request (e.g., 1024A, 1024B) using the indicator(e.g., 1010A, 1010B, 1010C) includes the electronic device (e.g., 1000)displaying (1116) a visual indicator (e.g., 1010A) (e.g., light) usingthe value of the characteristic (e.g., light color, position ofdisplayed light) corresponding to the user associated with the audiouser input request (e.g., 1024A, 1024B).

In some embodiments, the electronic device (e.g., 1000) responding tothe audio user input request (e.g., 1024A, 1024B) using the indicatorincludes the electronic device (e.g., 1000) providing (1118) an audioindicator (e.g., 1010B) (e.g., a voice, a sound) using the value of thecharacteristic (the value of the characteristic could be an accent,gender, pitch, voice, sound, or a particular digital assistant voice,such as American, Female digital assistant voice) corresponding to theuser (e.g., 1020, 1030) associated with the audio user input request(e.g., 1024A, 1024B). In some examples, the user selected the American,Female digital assistant voice in the digital assistant voice settingsas indicated in the user profile of the user (e.g., 1020, 1030).

In some embodiments, the indicator is a visual indicator (e.g., 1010A)and in response to the electronic device (e.g., 1000) receiving theaudio user input request (e.g., 1024A, 1024B) and prior to thedetermination that the audio user input request (e.g., 1024A, 1024B)corresponds to a particular user (e.g., 1020, 1030), the electronicdevice (e.g., 1000) displays the visual indicator (e.g., 1010A) with adefault value (e.g., white light) of the characteristic (e.g.,displaying a first light color when the digital assistant is activated).In some embodiments, the default value of the characteristic isdifferent from the first value and the second value.

In some embodiments, the characteristic of the audio indicator (e.g.,1010B) (e.g., the digital assistant providing confirmation using words)is a term (e.g., a word, a name of) corresponding to a user associatedwith (e.g., that provides) the audio user input request (e.g., 1024A,1024B).

Using the name of the user (e.g., 1020, 1030) in the digital assistantvoice confirmation indicator (e.g., 1010C) enables the digital assistantto provide feedback to confirm the digital assistant has identified thespecific user (e.g., 1020, 1030) speaking the command. Providingcustomized feedback to confirm the user (e.g., 1020, 1030) enhances theoperability of the digital assistant and makes the user-device interfacemore efficient (e.g., the specific user (e.g., 1020, 1030) knows thedigital assistant has processed the user's command (e.g., 1024A, 1024B).This reduces the cognitive burden on the user (e.g., 1020, 1030) as theuse of the user's name provides immediate confirmation that the task wascarried out and reduces the confusion when there are multiple users(e.g., 1020, 1030) speaking simultaneously or other speakers in thebackground. Further, the feedback of the state of the digital assistantallows the user (e.g., 1020, 1030) to use the digital assistant morequickly and efficiently.

In some embodiments, the electronic device (e.g., 1000) determines auser associated with the audio user input request based on one or moreof voice recognition, facial recognition, and a direction of the audiouser input request.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to betterenable users to control electronic devices. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used topersonalize device interactions. Accordingly, use of such personalinformation data enables users to more easily control electronicdevices. Further, other uses for personal information data that benefitthe user are also contemplated by the present disclosure. For instance,health and fitness data may be used to provide insights into a user'sgeneral wellness, or may be used as positive feedback to individualsusing technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof digital assistants, user gaze, and user profiles, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. In anotherexample, users can select not to provide personal information for userprofiles. In yet another example, users can select to limit the lengthof time personal information is maintained or entirely prohibit thedevelopment of a baseline profile. In addition to providing “opt in” and“opt out” options, the present disclosure contemplates providingnotifications relating to the access or use of personal information. Forinstance, a user may be notified upon downloading an app (e.g., adigital assistant app) that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, users caninteract with electronic devices based on non-personal information dataor a bare minimum amount of personal information.

What is claimed is:
 1. An electronic device, comprising: one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: while a first external device is in a firststate: receiving an audio user input request to perform a first command;and obtaining, using one or more camera sensors, first gaze information;and in accordance with a determination, using the first gazeinformation, that a set of one or more gaze criteria is met for thefirst external device: transmitting, based on the first command, aninstruction to transition the first external device from the first stateto a second state.
 2. The electronic device of claim 1, the one or moreprograms further including instructions for: in accordance with adetermination, using the first gaze information, that the set of one ormore gaze criteria is not met for the first external device: forgotransmitting the instruction to transition the first external devicefrom the first state to the second state.
 3. The electronic device ofclaim 1, wherein the set of one or more gaze criteria includes a fieldof view criterion that is met when a determined offset angle is lessthan a threshold offset angle, wherein the determined offset angle is anangle formed between: a line-of-sight of a gaze of a user, and acalculated line-of-sight from the user to the first external device. 4.The electronic device of claim 3, wherein the line-of-sight of the gazeof the user is based on a head position of the user.
 5. The electronicdevice of claim 1, wherein the set of one or more gaze criteria includesa dwell time criterion that is met for the first external device when adwell time of the gaze determined from the first gaze information ismore than a threshold period of time.
 6. The electronic device of claim1, the one or more programs further including instructions for: inaccordance with the determination that the set of one or more gazecriteria is met for the first external device, providing an indicationthat the set of one or more gaze criteria is met.
 7. The electronicdevice of claim 1, the one or more programs further includinginstructions for: subsequent to transmitting the instruction totransition the first external device from the first state to the secondstate, providing an indication that the first external device is in thesecond state.
 8. The electronic device of claim 6, wherein theindication is domain specific.
 9. The electronic device of claim 1,wherein electronic device is paired to the first external device. 10.The electronic device of claim 1, the one or more programs furtherincluding instructions for: while the first external device is in thefirst state and a second external device is in a third state: inaccordance with a determination, using the first gaze information, thatthe set of one or more gaze criteria is met for the second externaldevice: transmitting, based on the first command, an instruction totransition the second external device from the third state to a fourthstate; and in accordance with a determination, using the first gazeinformation, that the set of one or more gaze criteria is not met forthe second external device: forgo transmitting, based on the firstcommand, the instruction to transition the second external device fromthe third state to the fourth state.
 11. The electronic device of claim1, the one or more programs further including instructions for: whilethe first external device is in the second state and a second externaldevice is in a third state: receiving a second user input requestincluding a second command; obtaining, using one or more camera sensors,second gaze information; and in accordance with a determination, usingthe second gaze information, that the set of one or more gaze criteriais met for the second external device: transmitting, based on the secondcommand, an instruction to transition the second external device fromthe third state to a fourth state while the first external deviceremains in the second state.
 12. The electronic device of claim 11, theone or more programs further including instructions for: while thesecond external device is in the third state: in accordance with adetermination, using the second gaze information, that the set of one ormore gaze criteria is not met for the second external device: forgotransmitting the instruction to transition the second external devicefrom the third state to the fourth state.
 13. The electronic device ofclaim 10, the one or more programs further including instructions for:subsequent to transmitting the instruction to transition the secondexternal device from the third state to the fourth state, providing anindication that indicates that the second external device is in thefourth state.
 14. The electronic device of claim 1, the one or moreprograms further including instructions for: subsequent to transmittingthe instruction to transition the first external device from the firststate to the second state: receiving, from a third external device, anindication of an input received by the third external device; andtransmitting a second instruction, to the first external device based ona recency of the electronic device having instructed the first externaldevice.
 15. A non-transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device, the one or more programs including instructionsfor: while a first external device is in a first state: receiving anaudio user input request to perform a first command; and obtaining,using one or more camera sensors, first gaze information; and inaccordance with a determination, using the first gaze information, thata set of one or more gaze criteria is met for the first external device:transmitting, based on the first command, an instruction to transitionthe first external device from the first state to a second state.
 16. Amethod, comprising: at an electronic device: while a first externaldevice is in a first state: receiving an audio user input request toperform a first command; and obtaining, using one or more camerasensors, first gaze information; and in accordance with a determination,using the first gaze information, that a set of one or more gazecriteria is met for the first external device: transmitting, based onthe first command, an instruction to transition the first externaldevice from the first state to a second state.